Paddle MCP Server
Give any AI assistant direct access to the Paddle API over the Model Context Protocol.
This server gives AI assistants like Claude, Cursor, and Windsurf direct access to Paddle API operations — products, prices, subscriptions, customers, transactions, and more.
Three tools are exposed to your assistant:
search the API reference,
execute chained API calls in a sandbox, and
report_missing_tool
for telemetry.
Endpoint
A single MCP endpoint. Each host serves one environment — connect to
sandbox-mcp.paddle.com
for sandbox and
mcp.paddle.com
for live.
https://mcp.paddle.com/mcp
Authentication
There are two ways to authenticate: sign in with OAuth, or pass a Paddle API key as a bearer token.
OAuth
RecommendedPoint your client at the endpoint with no credentials. The first time it connects, a browser window opens and you sign in to Paddle — no API key to create, copy, or keep in a config file.
- A new connection gets read access by default, limited to what your Paddle user's role already permits.
- Change what a connection can do — or revoke it — from Paddle → Connectors → MCP in your dashboard.
- You may be asked to reauthorize from time to time.
API key
Prefer a long-lived credential, or running somewhere a browser can't open? Pass a
Paddle API key
in the Authorization
header on every request. Scope the key to the permissions you actually need — they are the only limit on
what the assistant can do.
Authorization: Bearer <your-paddle-api-key>Connect Your Client
Drop one of these configurations into your AI client.
Where a snippet carries no credentials, your client runs the OAuth flow on first connect.
Replace API_KEY with your own key.
claude mcp add --transport http paddle https://mcp.paddle.com/mcp
Then run /mcp
inside Claude Code to start the browser sign-in.
claude mcp add --transport http paddle https://mcp.paddle.com/mcp --header "Authorization: Bearer API_KEY"For more detailed setup instructions, see the full installation guide.