
This profile is part of our MCP server directory, within The MCP Guide. Profiles are checked against each vendor's own documentation. Need a server built? See MCP development.
The Paddle MCP server lets an AI app manage your Paddle Billing account. It covers products, prices, discounts, customers, transactions, subscriptions, adjustments and reports. Paddle publishes it as an open-source package you run locally.
Checked against: Paddle's MCP server README on 28 October 2026. eSEOspace did not install or test this server.
Key Takeaways
- Paddle says the server has "near parity with the Paddle API." It works with Paddle Billing, not Paddle Classic.
- It runs locally with
npx -y @paddle/paddle-mcpand a Paddle API key. - A built-in filter limits tools to
read-only,non-destructive(the default) orall. - Every tool is labeled as read-only or not, and as non-destructive or not.
- You choose
sandboxorproductionwhen you start the server.
At a glance
| Item | Detail |
|---|---|
| Publisher | Paddle |
| Official? | Yes |
| Hosting | Local package (@paddle/paddle-mcp on npm) |
| Transport | stdio |
| Sign-in | Paddle API key |
| Read or write | Both; filter to read-only or non-destructive |
| Price | No separate MCP price listed |
| Source code | PaddleHQ/paddle-mcp-server on GitHub (Apache-2.0) |
| Status | Not labeled |
What it can do
The README lists tools by resource. A sample:
- Products and prices:
list_products,create_product,get_product,update_product,list_prices,create_price,update_price,preview_prices. - Discounts:
list_discounts,create_discount,update_discount, plus discount group tools such asarchive_discount_group. - Customers:
list_customers,create_customer,get_customer,update_customer,list_credit_balances, plus address and business tools. - Transactions:
list_transactions,create_transaction,update_transaction,preview_transaction_create,revise_transaction,get_transaction_invoice. - Adjustments:
list_adjustments,create_adjustment,get_adjustment_credit_note. - Subscriptions:
list_subscriptions,get_subscription,update_subscription,cancel_subscription,pause_subscription,resume_subscription,activate_subscription,preview_subscription_update,create_subscription_charge,preview_subscription_charge. - Saved payment methods:
list_saved_payment_methods,get_saved_payment_method,delete_saved_payment_method. - Other groups: customer portal sessions, notification settings, events, notifications, simulations, reports and client-side tokens.
Each tool row in the README says whether it is non-destructive and whether it is read-only.
How to connect it
Create an API key in Paddle > Developer tools > Authentication. Paddle has separate sandbox and live dashboards for this.
Then add the server to your client. Paddle's recommended config for npx:
{
"mcpServers": {
"paddle": {
"command": "npx",
"args": [
"-y",
"@paddle/paddle-mcp",
"--api-key=your_api_key",
"--environment=sandbox",
"--tools=non-destructive"
]
}
}
}
You can also pass PADDLE_API_KEY, PADDLE_ENVIRONMENT and PADDLE_MCP_TOOLS as environment variables. Paddle offers one-click install links for Cursor and VS Code, and points to setup guides for Claude Desktop, Cursor and Windsurf (now Devin Desktop).
The --tools value accepts:
all: every tool.read-only: read operations only.non-destructive: reads plus safe writes (the default).- A comma-separated list of tool names, such as
list_products,get_product,create_product.
Security notes
- Destructive tools. Paddle marks tools such as
cancel_subscription,pause_subscription,update_transaction,revise_transactionanddelete_saved_payment_methodas not non-destructive. They are excluded under the default filter. - Money-related writes still allowed by default. The non-destructive set includes
create_transaction,create_adjustmentandcreate_subscription_charge. These are labeled safe because they add records, but they still bill or credit customers. Useread-onlyor an explicit list if you only need reporting. - No documented approval step. The README does not describe server-side human confirmation. Keep your client's tool approvals on.
- Sandbox first. Start with
--environment=sandboxand a sandbox key. - Key in config. The recommended config puts the API key in the args. Keep that file private. See secrets and credential leakage in MCP.
- What the spec says. The MCP tools specification says there SHOULD always be a human in the loop who can deny tool calls. The spec's security best practices also recommend scope minimization.
More guidance is in the MCP security center and excessive permissions in MCP servers.
Alternatives
- Stripe MCP server: remote, with OAuth and server-side approval for refunds.
- Chargebee MCP server: hosted subscription billing data lookups.
- Razorpay MCP server: remote or local, with a read-only flag.
Next step
Paddle's tool labels make it easy to start with read-only for revenue and churn questions. When you are ready for writes, list the exact tools by name. Our MCP readiness audit can help you pick them. See more in the MCP server directory.
Frequently asked questions
Does the Paddle MCP server work with Paddle Classic?
No. Paddle says it works with Paddle Billing only and points Classic users to the Classic API reference.
What does "non-destructive" mean here?
It means reads plus writes that Paddle labels safe, such as creating records. Updates, cancellations, pauses and deletions are excluded. It is the default setting.
Is there a hosted version?
The README documents a local server run with npx. We did not find a hosted Paddle MCP endpoint in the docs we checked.
Can I test without touching live data?
Yes. Set --environment=sandbox and use a sandbox API key from Paddle's sandbox dashboard.











