MCP Server for Paddle Billing
Most payments and commerce work still happens through a UI a human drives. Paddle MCP server moves it into the conversation instead. MCP Server for Paddle Billing.
Paddle Billing is the developer-first merchant of record. We take care of payments, tax, subscriptions, and metrics with one unified API that does it all.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
The server publishes 4 tools. What each one is for:
all — All tools are availableread-only — Only read operations are availablenon-destructive — Read operations and safe write operations are available (default)Operation — ToolConfiguration is passed through the environment: PADDLE_API_KEY, PADDLE_ENVIRONMENT, PADDLE_MCP_TOOLS. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the payments and commerce options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Paddle's toolset — all, read-only, non-destructive and 1 more — is a fair guide to whether it matches your workflow. It is maintained by PaddleHQ; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Paddle's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| all | All tools are available |
| read-only | Only read operations are available |
| non-destructive | Read operations and safe write operations are available (default) |
| Operation | Tool |
{
"mcpServers": {
"paddle": {
"command": "npx",
"args": [
"-y",
"@paddle/paddle-mcp",
"--api-key=your_api_key",
"--environment=sandbox",
"--tools=non-destructive"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PADDLE_API_KEY | Credential the server authenticates with. | Yes |
| PADDLE_ENVIRONMENT | Configuration value read at startup. | Optional |
| PADDLE_MCP_TOOLS | Configuration value read at startup. | Optional |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.