MCP Billing Orchestrator

The Billing.net MCP Orchestrator connects to 11+ billing MCP servers through native MCP-to-MCP communication. Instead of implementing each provider's REST API, we call their MCP servers directly, with intelligent fallbacks to REST when needed.

Why MCP Matters for Billing Automation

Traditional billing APIs are rigid and tied to a single provider. With MCP, billing becomes a universal language. Agents or apps can issue commands like:

{
  "command": "invoice.create",
  "params": {
    "customer": "@acme",
    "amount": 1200,
    "currency": "usd"
  }
}

…and the Billing.net MCP Server routes that to your preferred provider — Stripe, LemonSqueezy, Paddle, or even crypto — through plug-in adapters.

How Billing.net Implements MCP

Billing.net exposes a REST + MCP endpoint at:

It validates the request, logs it, then delegates to a provider module. You can add or override adapters for payments, invoicing, tax, email, or analytics — all written in Python or TypeScript.

Architecture

The server translates structured commands into actionable billing calls. Each provider (Stripe, LemonSqueezy, TaxJar, Postmark, etc.) registers through a lightweight interface.

Supported Providers

Getting Started

Self-host the open-source server:

git clone https://github.com/billing-net/billing.net
cd backend && ./run.sh

Or use Billing Cloud, our managed instance with instant API keys.

Own your billing logic — not just your payments.