Add the Paddle MCP server to Windsurf

Config last verified Jun 1, 2026

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

Prerequisites

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

Setup

1. Open `~/.codeium/windsurf/mcp_config.json`

On Windows the file lives at %USERPROFILE%\.codeium\windsurf\mcp_config.json.

2. Add this configuration

Add to ~/.codeium/windsurf/mcp_config.json

~/.codeium/windsurf/mcp_config.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 Windsurf and confirm the Paddle tools load.

Gotchas

Windsurf's Cascade reads MCP servers from an "mcpServers" object in ~/.codeium/windsurf/mcp_config.json. Unlike most clients, remote servers are configured with the "serverUrl" field rather than "url", so a config that uses "url" silently fails to connect. Native remote transport is supported without an OAuth flow.

← Back to the Paddle MCP server