Interact with the Paddle API using AI assistants like Claude, or in AI-powered IDEs like Cursor. Manage product catalog, billing and subscriptions, and reports.
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.
This is a Model Context Protocol (MCP) server that provides tools for interacting with the Paddle API.
Important: This MCP server works with Paddle Billing. It does not support Paddle Classic. To work with Paddle Classic, see: Paddle Classic API reference
To use the MCP server, you’ll need an API key. You can create and manage API keys in Paddle > Developer tools > Authentication:
To run the server in a client like Claude Desktop, Cursor or Windsurf, add the following to your MCP config:
{
"mcpServers": {
"paddle": {
"command": "npx",
"args": ["-y", "@paddle/paddle-mcp", "--api-key=PADDLE_API_KEY", "--environment=(sandbox|production)"]
}
}
}
Replace PADDLE_API_KEY with your API key, and pass the correct value as environment.
For detailed setup guides, see:
Install dependencies:
pnpm install
Build the server:
pnpm build
Update client to use the local build:
{
"mcpServers": {
"paddle": {
"command": "node",
"args": ["path/to/paddle-mcp-server/build/index.js"],
"env": {
"PADDLE_API_KEY": "your_api_key",
"PADDLE_ENVIRONMENT": "sandbox"
}
}
}
}
To debug the MCP server, you can use the MCP Inspector tool:
Run the server with the inspector:
pnpm inspector
Open the provided URL in your browser to view and debug the MCP requests and responses.
Include the --api-key and --environment arguments.
Execute a secure shell in Claude Desktop using the Model Context Protocol.
A Model Context Protocol (MCP) server that provides tools for interacting with the Twitch API using the Helix API.
A open-source library enabling AI models to control hardware devices via serial communication using the MCP protocol. Initial support for Raspberry Pi Pico.
