Add the Paddle MCP server to Cursor

Config last verified Jun 1, 2026

The exact config to run Paddle in Cursor — paste it in, restart, and the tools load.

Prerequisites

Cursor installed.
PADDLE_API_KEY — Paddle API key for the target account.

Setup

1. Open `~/.cursor/mcp.json`

2. Add this configuration

Add to ~/.cursor/mcp.json

~/.cursor/mcp.json

json

{
  "mcpServers": {
    "paddle": {
      "command": "npx",
      "args": [
        "-y",
        "@paddle/paddle-mcp",
        "--api-key=PADDLE_API_KEY",
        "--environment=sandbox",
        "--tools=non-destructive"
      ],
      "env": {
        "PADDLE_API_KEY": "<PADDLE_API_KEY>",
        "PADDLE_ENVIRONMENT": "<PADDLE_ENVIRONMENT>",
        "PADDLE_MCP_TOOLS": "<PADDLE_MCP_TOOLS>"
      }
    }
  }
}

3. Restart Cursor and confirm the Paddle tools load.

Gotchas

Cursor keeps MCP servers under an "mcpServers" object in ~/.cursor/mcp.json for global use, and also reads a project-scoped .cursor/mcp.json so a repository can ship its own servers. Remote servers are configured with a bare "url" field and connect natively, with OAuth handled in-app when a server requires it.

← Back to the Paddle MCP server