Paddle MCP Server

What is Paddle MCP Server about?

Provides a Model Context Protocol (MCP) server that exposes Paddle Billing functionality, enabling AI assistants and IDEs to list and create products, prices, customers, transactions, subscriptions, and generate custom financial reports.

How to use Paddle MCP Server?

Obtain a Paddle API key from the Paddle dashboard (sandbox or live).
Add an MCP server entry to your client configuration (Claude Desktop, Cursor, Windsurf, etc.) using the npx command.
Run the server via npx @paddle/paddle-mcp --api-key=YOUR_KEY --environment=sandbox|production.
Invoke the exposed operations from your AI assistant or IDE to interact with the Paddle Billing API.

Key features of Paddle MCP Server

List and create products in the Paddle catalog
List and create pricing for products
Retrieve customers, transactions, and subscriptions
Generate custom financial analysis reports
Simple installation via npx
Supports both sandbox and production environments

Use cases of Paddle MCP Server

Automating product catalog management directly from a coding environment
Building AI‑driven billing dashboards that query Paddle data on demand
Generating real‑time financial reports for stakeholders via chat assistants
Integrating subscription lifecycle handling into development workflows

FAQ from the Paddle MCP Server

Q: Does this server work with Paddle Classic? A: No, it only supports Paddle Billing. Use the Paddle Classic API reference for classic support.

Q: Which command should I use to run the server? A: Prefer npx as shown in the installation example.

Q: How do I switch between sandbox and production? A: Pass --environment=sandbox or --environment=production when starting the server, or set the PADDLE_ENVIRONMENT environment variable.

Q: What runtime is required? A: Node.js with npm (or pnpm) – the server is distributed as an npm package.

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.

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

Features

List products in your Paddle catalog
Create new products
List prices for products
Create new prices for products
List customers
List transactions
List subscriptions
Create custom reports for financial analysis

Installation

To use the MCP server, you'll need an API key. You can create and manage API keys in Paddle > Developer tools > Authentication:

Sandbox: https://sandbox-vendors.paddle.com/authentication-v2
Live: https://vendors.paddle.com/authentication-v2

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:

Development

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"
      }
    }
  }
}

Debugging

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.