Paddle MCP Server

Content

The Paddle MCP Server is the official Model Context Protocol server maintained by Paddle. It gives LLMs and agentic clients near-parity access to the Paddle Billing API — Paddle is a developer-first merchant of record that handles payments, tax, and subscriptions — so an agent can manage the product catalog, view customers and purchases, handle subscription, payment, and refund workflows, create and adjust transactions, and generate financial reports.

The project is written in TypeScript, distributed as the npm package @paddle/paddle-mcp (v0.1.6), and licensed under Apache 2.0. It runs over stdio via npx, authenticates with a Paddle API key, targets either the sandbox or production environment, and exposes a tool-permission filter (read-only, non-destructive, or all) so you can bound what the agent may do. It supports Paddle Billing (not Paddle Classic).

Source Review

The following real repository and package sources were fetched and reviewed for this entry:

• README.md — install methods (command-line args and environment variables), the config blocks, the --tools/PADDLE_MCP_TOOLS permission modes, environment settings, and the full tool catalog.
• npm: @paddle/paddle-mcp — package name and version (0.1.6), Apache-2.0 license, and the paddle bin entry.
• LICENSE — Apache License 2.0.

Repository facts confirmed at review time: official PaddleHQ organization, default branch main, not archived, and released as @paddle/paddle-mcp v0.1.6 on npm.

Features

• Catalog management — create and update products, prices, and discounts (e.g. create_product, create_price, create_discount).
• Customers & businesses — view and manage customers, businesses, and addresses (e.g. create_customer, get_customer, create_business).
• Subscriptions — inspect, activate, cancel, and charge subscriptions (e.g. activate_subscription, cancel_subscription, create_subscription_charge).
• Transactions & adjustments — create transactions and issue adjustments such as refunds and credits (e.g. create_transaction, create_adjustment).
• Reports — generate financial and operational reports (e.g. create_report).
• Simulations — create and run integration simulations (e.g. create_simulation, create_simulation_run).
• Tool-permission filter — read-only, non-destructive (default), all, or a comma-separated allowlist of specific tools via --tools / PADDLE_MCP_TOOLS.
• Sandbox or production — target sandbox for development or production for live data via --environment / PADDLE_ENVIRONMENT.
• One-command install — runs via npx -y @paddle/paddle-mcp with no clone or build step.

Installation

Run the published package with npx, passing your API key, environment, and tool mode as arguments (recommended):

npx -y @paddle/paddle-mcp --api-key=YOUR_API_KEY --environment=sandbox --tools=non-destructive

Add it to an MCP client (e.g. Cursor / Claude Desktop) using command-line arguments:

{
  "mcpServers": {
    "paddle": {
      "command": "npx",
      "args": [
        "-y",
        "@paddle/paddle-mcp",
        "--api-key=YOUR_API_KEY",
        "--environment=sandbox",
        "--tools=non-destructive"
      ]
    }
  }
}

Or configure it with environment variables instead:

{
  "mcpServers": {
    "paddle": {
      "command": "npx",
      "args": ["-y", "@paddle/paddle-mcp"],
      "env": {
        "PADDLE_API_KEY": "YOUR_API_KEY",
        "PADDLE_ENVIRONMENT": "sandbox",
        "PADDLE_MCP_TOOLS": "non-destructive"
      }
    }
  }
}

Create and manage API keys in Paddle > Developer tools > Authentication (sandbox and live are separate). Accepted --tools / PADDLE_MCP_TOOLS values are all, read-only, non-destructive (default), or a comma-separated list of specific tool names.

Use Cases

• Conversational billing ops — inspect customers, subscriptions, and transactions and make changes in natural language.
• Catalog authoring — create and adjust products, prices, and discounts from an agentic workflow.
• Refunds and adjustments — issue credits or refunds through adjustment tools (with appropriate permissions).
• Financial reporting — generate revenue and operational reports for analysis.
• Integration testing — run simulations against the sandbox environment while building a Paddle integration.

Safety and Privacy

• Acts on real billing data. With write permissions the server can create and modify products, customers, subscriptions, and transactions; adjustment/transaction tools can move real money.
• Permission filter is a first-class control. Use --tools=read-only or the default non-destructive unless a destructive action is intended; all enables every operation.
• Sandbox first. Develop with --environment=sandbox and a sandbox key; switch to production only deliberately.
• API key is sensitive. It grants broad account access — keep client config out of version control and restrict access.
• Data flows to the model. Customer, business, subscription, transaction, and report data (including personal and financial details) is returned to the LLM/MCP client, so avoid exposing production data unnecessarily.

Duplicate Check

No existing entry in the directory matches this server. A search of all directory entries for "paddle" across slugs, titles, repository URLs, and install commands returned no results, and there is no prior entry pointing at github.com/PaddleHQ/paddle-mcp-server or the npm package @paddle/paddle-mcp. This is therefore a net-new, non-duplicate entry.

• Source repositorygithub.com 2026-07-08T14:53:09-07:00
• Documentationgithub.com
• Websitepaddle.com
• Submitted by davion-knight2026-07-08