GitHub - PaddleHQ/paddle-mcp-server: 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. (original) (raw)

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

Install MCP Server

Features

Installation

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:

Development

  1. Install dependencies:
  2. Build the server:
  3. 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:

  1. Run the server with the inspector:
  2. Open the provided URL in your browser to view and debug the MCP requests and responses.
  3. Include the --api-key and --environment arguments.

Learn more