MCP.so
Sign In

MCP Server for Paddle Billing

@PaddleHQ

About MCP Server for Paddle Billing

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.

Config

Add this server to your MCP-compatible client using the configuration below.

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

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP Server for Paddle Billing?

MCP Server for Paddle Billing is a Model Context Protocol server that provides LLMs and AI agents with tools for interacting with the Paddle API. It is intended for developers using Paddle Billing (not Paddle Classic) to manage payments, subscriptions, and billing operations through natural language.

How to use MCP Server for Paddle Billing?

Install with a Paddle API key (from sandbox or live vendor portal) and add the server configuration to your MCP settings file. Use one-click installation in Cursor or VS Code, or manually configure the npx command with environment variables PADDLE_API_KEY, PADDLE_ENVIRONMENT, and PADDLE_MCP_TOOLS. Tools are invoked via an AI assistant.

Key features of MCP Server for Paddle Billing

  • Manage full Paddle catalog (products, prices, discounts)
  • View customer, purchase, and provisioning information
  • Handle subscription, payment, and refund workflows
  • Debug billing and order management issues
  • Create and adjust transactions in conversation
  • Generate financial reports for operational insights

Use cases of MCP Server for Paddle Billing

  • Automate product and price management through chat
  • Resolve subscription or payment issues with AI assistance
  • Generate custom financial reports without API coding
  • Build and test Paddle integrations faster
  • Pull customer data and transaction details on demand

FAQ from MCP Server for Paddle Billing

Does this server work with Paddle Classic?

No, it only supports Paddle Billing. For Paddle Classic, use the separate Paddle Classic API reference.

What are the runtime requirements?

The server runs via npx (Node.js) and requires an active Paddle API key (sandbox or live).

How is the server authenticated?

Authentication is done via the PADDLE_API_KEY environment variable, set to a valid Paddle API key.

What transport does the server use?

It uses the standard stdio transport as defined by the MCP specification.

Are there any tool restrictions based on the configuration?

Yes. The PADDLE_MCP_TOOLS environment variable can be set to "non-destructive" to enable only non-destructive tools (e.g., list, get, create) while blocking update, cancel, and delete operations.

Frequently asked questions

Does this server work with Paddle Classic?

No, it only supports Paddle Billing. For Paddle Classic, use the separate Paddle Classic API reference.

What are the runtime requirements?

The server runs via `npx` (Node.js) and requires an active Paddle API key (sandbox or live).

How is the server authenticated?

Authentication is done via the `PADDLE_API_KEY` environment variable, set to a valid Paddle API key.

What transport does the server use?

It uses the standard stdio transport as defined by the MCP specification.

Are there any tool restrictions based on the configuration?

Yes. The `PADDLE_MCP_TOOLS` environment variable can be set to `"non-destructive"` to enable only non-destructive tools (e.g., list, get, create) while blocking update, cancel, and delete operations.

Comments

More Developer Tools MCP servers