Dodo Payments MCP Server

Use the Dodo Payments remote Model Context Protocol (MCP) server to give AI agents access to the Dodo Payments docs and your account. Agents can look up how a feature works, then create payments, manage subscriptions, issue refunds and more. The server lives at https://mcp.dodopayments.com/mcp. We recommend naming it dodopayments in your client.

The MCP server uses OAuth. When you add the server, your client opens your browser so you can sign in and approve access. You never copy an API key into your agent.

Connect Your Agent

The Dodo Agent Plugin (0.7.0 and later) adds this server and the dodo-payments skill for you. To connect a client yourself, pick it below.

Run:

claude mcp add --transport http dodopayments https://mcp.dodopayments.com/mcp

To sign in, run /mcp inside Claude Code and pick dodopayments.

Add the following to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json to make Dodo Payments available in every project:

{
  "mcpServers": {
    "dodopayments": {
      "url": "https://mcp.dodopayments.com/mcp"
    }
  }
}

Open Cursor’s MCP settings and connect to dodopayments to sign in.

Add the following to .vscode/mcp.json in your workspace, or run MCP: Add Server from the command palette:

{
  "servers": {
    "dodopayments": {
      "type": "http",
      "url": "https://mcp.dodopayments.com/mcp"
    }
  }
}

Start the server from the MCP UI in VS Code to sign in.

Run:

codex mcp add dodopayments --url https://mcp.dodopayments.com/mcp

To sign in, run:

codex mcp login dodopayments

Add the server to opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dodopayments": {
      "type": "remote",
      "url": "https://mcp.dodopayments.com/mcp",
      "enabled": true
    }
  }
}

To sign in, run:

opencode mcp auth dodopayments

Run:

gemini mcp add --transport http dodopayments https://mcp.dodopayments.com/mcp

To sign in, run /mcp auth dodopayments inside Gemini CLI.

Open Settings, then Connectors, select Add custom connector, and enter:

Name: dodopayments
MCP server URL: https://mcp.dodopayments.com/mcp

Save the connector, select Connect, and sign in in the browser.

If your client accepts a remote MCP URL, add https://mcp.dodopayments.com/mcp.If it only supports local commands, use the mcp-remote bridge. This needs Node.js 18 or later:

{
  "mcpServers": {
    "dodopayments": {
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://mcp.dodopayments.com/mcp"]
    }
  }
}

See modelcontextprotocol.io/clients for other clients.

Approve the Connection

The first sign-in opens the Dodo Payments consent page in your browser. Your team role caps what you can grant, so a connection can never do more than you can.

Choose the business the AI client can use.

Consent page, step 1 of 4: choose the business that the app can access

Choose the mode: test mode or live mode.

Consent page, step 2: Choose a Mode, with one choice of Live Mode or Test Mode

Set the permissions: Read, Write, or Customise to pick a level for each resource.

Consent page, step 3 of 4: Set Permissions, with Read, Write, and Customise options and resource groups such as Payments and Catalog

Review and authorize the connection.

Start with test mode and Read access. Approve live mode or Write access only when you need them.

Each connection holds one mode. To work in the other mode, add a second connection and approve the other mode.

Access tokens expire after 1 hour. Refresh tokens rotate on each use.
Your client never holds an API key. For each call, the MCP server exchanges your token for an API token that lasts 5 minutes and carries only the permissions you approved.
You can revoke a connection at any time in Settings → Connected Apps. Revoke stops new tokens at once, and tokens already issued stop working within about a minute. See Connected Apps.

How the Tools Work

Dodo Payments has many API operations. Instead of sending every operation and its input schema to your agent at the start of every conversation, the server gives it a few tools. The agent finds what it needs, then writes a short TypeScript snippet to call it. This is code mode.

Tool	What it does
`search_docs`	Searches the Dodo Payments guides.
`read_docs_page`	Reads a documentation page as Markdown.
`search`	Searches SDK and API methods, with their parameters.
`execute`	Runs TypeScript SDK code against your account in a sandbox.
`feedback`	Sends your agent’s feedback about Dodo Payments, these tools or the docs.

The server asks your client to sign in before it lists the tools, so your client starts the OAuth sign-in when you add the server. 1. Search The agent calls search_docs to find the right guide and read_docs_page to read it. It calls search to find the SDK methods for its task, such as “list a customer’s active subscriptions”, and their exact parameters. 2. Execute The agent calls execute with code that defines async function run(client) { ... }, where client is an authenticated Dodo Payments SDK client. It can chain calls, page through results and return only the fields it needs.

async function run(client) {
  const page = await client.payments.list({ page_size: 10 });
  return page.items.map((p) => ({ id: p.payment_id, status: p.status }));
}

Code runs in an isolated sandbox. It can only call the Dodo Payments SDK, with the access you approved on the consent page.

Agents can chain several API calls, handle conditional logic and do calculations in one script, without a round trip to the model for each step.

What `execute` Can Do

execute gives your agent the Dodo Payments TypeScript SDK, limited to the permissions you approved. The SDK covers these resources:

Area	Resources
Payments and checkout	Payments, checkout sessions, refunds, disputes
Subscriptions	Subscriptions, add-ons
Customers	Customers, entitlements
Catalog and pricing	Products, product collections, discounts, brands
Usage and credits	Meters, usage events, credit entitlements, balance ledger
Software licensing	Licenses
Operations	Webhooks, payouts, blocklist, moderation

Use the search tool to see the exact methods and parameters available for each resource. See the API Reference for the full list of endpoints.

Telemetry and Feedback

The feedback tool lets your agent tell us what worked and what didn’t, about Dodo Payments, the MCP tools or these docs. It needs sign-in. Before the text is stored, the server removes emails, IDs and keys from it. The Dodo Payments team reads and triages each message, with your business ID so we can follow up. The tool returns a reference ID. Ask your agent to write feedback without customer names, emails or IDs. Removal matches the shape of an identifier, not its meaning, so a name written in plain words can still pass.

Docs-Only Access

If your client can’t sign in with OAuth, or you only want docs search, connect to https://mcp.dodopayments.com/mcp?auth=optional. Then search_docs, read_docs_page and search work without an account, and execute and feedback ask you to sign in. https://knowledge.dodopayments.com/mcp is another docs-only address that needs no account.

Advanced: Local Server with an API Key

Run the MCP server yourself when you need a stdio server, an air-gapped setup, or a fixed API key. This setup uses an API key from Developer → API Keys and does not use the OAuth sign-in. Install the server with NPM or Docker.

NPM Package

Install and run the MCP server locally.

The local server runs your code in a Deno sandbox. Install Deno 2.8 or earlier and make sure deno is on your PATH; the sandbox fails to start on Deno 2.9 and later. Local code execution works on macOS and Linux only. On Windows, use the remote server or run the local server under WSL2.

NPX (No Installation)
MCP Client Configuration

# Set your environment variables
export DODO_PAYMENTS_API_KEY="dodo_test_..."
export DODO_PAYMENTS_WEBHOOK_KEY="your_webhook_key"
export DODO_PAYMENTS_ENVIRONMENT="test_mode"

# Run the latest version
npx -y dodopayments-mcp@latest

{
  "mcpServers": {
    "dodopayments": {
      "command": "npx",
      "args": ["-y", "dodopayments-mcp@latest"],
      "env": {
        "DODO_PAYMENTS_API_KEY": "dodo_test_...",
        "DODO_PAYMENTS_WEBHOOK_KEY": "your_webhook_key",
        "DODO_PAYMENTS_ENVIRONMENT": "test_mode"
      }
    }
  }
}

Use @latest to always pull the most recent version, or pin to a specific version like @2.51.0 for stability.

Docker

Run the MCP server in a container.

# Pull the latest image
docker pull ghcr.io/dodopayments/mcp:latest

# Run the container (-i keeps stdin open for the stdio transport)
docker run -i -e DODO_PAYMENTS_API_KEY="dodo_test_..." \
  -e DODO_PAYMENTS_WEBHOOK_KEY="your_webhook_key" \
  -e DODO_PAYMENTS_ENVIRONMENT="test_mode" \
  ghcr.io/dodopayments/mcp:latest

Docker images are available on GitHub Container Registry.

Never commit API keys to version control. Keep them in environment variables or a secret manager, use test mode keys during development, and rotate keys from the dashboard. If you run the server remotely, always require the Authorization or x-dodo-payments-api-key header and serve it over HTTPS.

Environment Variables

Configure the MCP server behavior using environment variables.

Variable	Description	Required
`DODO_PAYMENTS_API_KEY`	Your Dodo Payments API key	Yes
`DODO_PAYMENTS_WEBHOOK_KEY`	Your webhook signing key	No
`DODO_PAYMENTS_ENVIRONMENT`	`live_mode` or `test_mode`; defaults to `live_mode`	No

Running Remotely

Deploy the MCP server as a remote HTTP server for web-based clients or agentic workflows.

# Start as remote server
npx -y dodopayments-mcp --transport=http

# Specify a custom port
npx -y dodopayments-mcp --transport=http --port=3000

Remote Server Configuration

Once deployed, clients can connect using the server URL:

{
  "mcpServers": {
    "dodopayments": {
      "url": "http://localhost:3000",
      "headers": {
        "Authorization": "Bearer dodo_test_..."
      }
    }
  }
}

Authorization Headers

The remote server accepts authentication via the following headers:

Header	Purpose
`Authorization`	Bearer token authentication
`x-dodo-payments-api-key`	Direct API key header

Resources

API Reference

Explore the complete Dodo Payments API documentation

MCP Protocol

Learn more about the Model Context Protocol standard

GitHub Repository

View the MCP server source code and contribute

NPM Package

Install the MCP server from NPM

Getting Started

Features

Integrate

Merchant of Record

Miscellaneous

Connect Your Agent

Approve the Connection

How the Tools Work

What `execute` Can Do

Telemetry and Feedback

Docs-Only Access

Advanced: Local Server with an API Key

NPM Package

Docker

Environment Variables

Running Remotely

Remote Server Configuration

Authorization Headers

Resources

API Reference

MCP Protocol

GitHub Repository

NPM Package

Connect Your Agent

Approve the Connection

How the Sign-In Is Secured

How the Tools Work

What execute Can Do

Telemetry and Feedback

Docs-Only Access

Advanced: Local Server with an API Key

NPM Package

Docker

Environment Variables

Running Remotely

Remote Server Configuration

Authorization Headers

Resources

API Reference

MCP Protocol

GitHub Repository

NPM Package

What `execute` Can Do