Dodo Payments
OfficialUsed for schema validation in custom endpoints, allowing developers to define input schemas for tools using Zod's type system which are then converted to JSON Schema through the zodToJsonSchema function.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Dodo Paymentscreate a subscription for customer cus_123 for the pro plan"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Dodo Payments TypeScript MCP Server
Installation
Direct invocation
You can run the MCP Server directly via npx:
export DODO_PAYMENTS_API_KEY="My Bearer Token"
export DODO_PAYMENTS_WEBHOOK_KEY="My Webhook Key"
export DODO_PAYMENTS_ENVIRONMENT="live_mode"
npx -y dodopayments-mcp@latestVia MCP Client
There is a partial list of existing clients at modelcontextprotocol.io. If you already have a client, consult their documentation to install the MCP server.
For clients with a configuration JSON, it might look something like this:
{
"mcpServers": {
"dodopayments_api": {
"command": "npx",
"args": ["-y", "dodopayments-mcp"],
"env": {
"DODO_PAYMENTS_API_KEY": "My Bearer Token",
"DODO_PAYMENTS_WEBHOOK_KEY": "My Webhook Key",
"DODO_PAYMENTS_ENVIRONMENT": "live_mode"
}
}
}
}Cursor
If you use Cursor, you can install the MCP server by using the button below. You will need to set your environment variables
in Cursor's mcp.json, which can be found in Cursor Settings > Tools & MCP > New MCP Server.
VS Code
If you use MCP, you can install the MCP server by clicking the link below. You will need to set your environment variables
in VS Code's mcp.json, which can be found via Command Palette > MCP: Open User Configuration.
Claude Code
If you use Claude Code, you can install the MCP server by running the command below in your terminal. You will need to set your
environment variables in Claude Code's .claude.json, which can be found in your home directory.
claude mcp add dodopayments_mcp_api --env DODO_PAYMENTS_API_KEY="My Bearer Token" DODO_PAYMENTS_WEBHOOK_KEY="My Webhook Key" -- npx -y dodopayments-mcpRelated MCP server: Lightning Enable MCP
Code Mode
This MCP server is built on the "Code Mode" tool scheme. In this MCP Server, your agent will write code against the TypeScript SDK, which will then be executed in an isolated sandbox. To accomplish this, the server will expose two tools to your agent:
The first tool is a docs search tool, which can be used to generically query for documentation about your API/SDK.
The second tool is a code tool, where the agent can write code against the TypeScript SDK. The code will be executed in a sandbox environment without web or filesystem access. Then, anything the code returns or prints will be returned to the agent as the result of the tool call.
Using this scheme, agents are capable of performing very complex tasks deterministically and repeatably.
Requirements for the code tool
The execute tool runs your code in a local Deno sandbox, so Deno must be
available. The server looks for it in this order:
A
denobinary on yourPATH.A
denobinary from thedenonpm package, when it is installed into the samenode_modulestree as this package.
If neither is found, the execute tool returns an error while every other tool, including
documentation search, keeps working.
Step 2 does not apply when you launch the server withnpx or install it globally, because the
server then resolves from its own cache directory rather than from your project. Since
npx -y dodopayments-mcp is the most common way to run it, installing Deno on your PATH is the
recommended setup.
UseDeno 2.8 or earlier for now. On Deno 2.9+ the sandbox fails to start, because binding the
worker's Unix socket began requiring --allow-net permission for that socket, which the worker
does not grant. Note that npm install deno currently installs an affected version. Tracked in
#330.
Local code execution is supported onmacOS and Linux only. It does not work on Windows,
because the sandbox communicates with the Deno subprocess over a Unix domain socket and Deno
cannot listen on one when running on Windows (see
denoland/deno#18236). Installing Deno does not
change this. On Windows, run the server under WSL2, or call the REST API or the dodopayments
SDK directly.
Running remotely
Launching the client with --transport=http launches the server as a remote server using Streamable HTTP transport. The --port setting can choose the port it will run on, and the --socket setting allows it to run on a Unix socket.
Authorization can be provided via the Authorization header using the Bearer scheme.
Additionally, authorization can be provided via the following headers:
Header | Equivalent client option | Security scheme |
|
| API_KEY |
A configuration JSON for this server might look like this, assuming the server is hosted at http://localhost:3000:
{
"mcpServers": {
"dodopayments_api": {
"url": "http://localhost:3000",
"headers": {
"Authorization": "Bearer <auth value>"
}
}
}
}This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityCmaintenanceMCP server for AgentPay — the payment gateway for autonomous AI agents. Fund a wallet once, give your agent the key, and it discovers, provisions, and pays for tool APIs on its own. One key, every tool.Last updated1121MIT
- AlicenseAqualityBmaintenanceMCP server that enables AI agents to make autonomous Bitcoin Lightning Network payments using the L402 protocol. Agents can pay for API access, purchase resources, and complete transactions without human intervention — invoice comes in, sats go out, done.Last updated179MIT

PayLink MCP Serverofficial
Flicense-qualityDmaintenanceOpen-source MCP server that streamlines payment integration for AI agents and financial apps in Africa, providing unified tools for providers like M-Pesa.Last updated1- Flicense-qualityBmaintenanceAn MCP server that enables AI agents to safely interact with a double-entry payments ledger, enforcing idempotency, policy-based access control, and human-in-the-loop approval for high-value actions.Last updated
Related MCP Connectors
Agent Commerce Protocol MCP — bridges Stripe ACP + Google AP2 + Coinbase x402 for agent payments
Agent-commerce MCP server for x402/USDC payments and affiliate splits on Base.
MCP Server for agents to onboard, pay, and provision services autonomously with InFlow
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dodopayments/dodopayments-typescript'
If you have feedback or need assistance with the MCP directory API, please join our Discord server