Dodo Payments
Live Dodo Payments API for AI agents — payments, subscriptions, customers, products, refunds, license keys, and usage-based billing via browser OAuth (no API key needed) plus a companion documentation search server.
Dodo Payments Agent Plugin
The official Dodo Payments plugin for AI coding agents. Installs eight integration skills and two MCP servers across Claude Code, Codex CLI, Cursor, and OpenCode from a single source of truth.
What you get
- Dodo Payments API MCP server - Live API access (payments, subscriptions, customers, products, refunds, licenses, usage). Authenticates via browser OAuth, no local credentials required.
- Dodo Knowledge MCP server - No credentials. Semantic search over the current Dodo Payments documentation.
- Eight agent skills - Written as
SKILL.mdfiles with YAML frontmatter. Your agent loads the relevant skill on its own when a task calls for it.
Install
Claude Code
claude plugins marketplace add dodopayments/dodo-agent-plugin
claude plugins install dodopayments@dodopayments
The API MCP server uses browser OAuth by default, so no keys are required at install time. The first time your agent calls a Dodo tool, you'll be prompted to sign in.
Codex CLI
Codex installs plugins in two steps: register the marketplace from your shell, then install the plugin from inside the Codex TUI.
-
Register the marketplace:
codex plugin marketplace add dodopayments/dodo-agent-plugin -
Open Codex and run the
/pluginsslash command:codexThen type
/plugins, switch to the Dodo Payments marketplace, select the dodopayments plugin, and choose Install plugin.
If you previously added the marketplace before this fix landed and the plugin doesn't appear under /plugins, refresh it:
codex plugin marketplace upgrade dodopayments
Codex CLI does not have a
codex plugin installsubcommand. Plugin installation always happens through the in-TUI/pluginsflow (official docs).
Cursor
Manual install:
git clone https://github.com/dodopayments/dodo-agent-plugin.git ~/.cursor/plugins/local/dodo-agent-plugin
Restart Cursor. The plugin loads skills from .claude/skills/ (via Cursor's Claude Code compat) and MCP servers from .mcp.json.
OpenCode
OpenCode distributes via npm. Add the plugin to your opencode.json:
{
"$schema": "https://opencode.ai/config.json",
"plugin": ["@dodopayments/opencode-plugin"]
}
Restart OpenCode. Both MCP servers (dodopayments-api, dodo-knowledge) are registered automatically via the plugin's config hook, and the eight skills are auto-discovered from the installed package. No manual mcp block required.
If you prefer the local stdio API server with your own API key instead of the default remote OAuth server, declare dodopayments-api yourself in opencode.json - your entry wins over the plugin default:
{
"plugin": ["@dodopayments/opencode-plugin"],
"mcp": {
"dodopayments-api": {
"type": "local",
"command": ["npx", "-y", "dodopayments-mcp@latest"],
"environment": {
"DODO_PAYMENTS_API_KEY": "dodo_test_...",
"DODO_PAYMENTS_WEBHOOK_KEY": "whsec_...",
"DODO_PAYMENTS_ENVIRONMENT": "test_mode"
},
"enabled": true
}
}
}
Included Skills
| Skill | Description |
|---|---|
best-practices | Comprehensive guide to integrating Dodo Payments with best practices |
checkout-integration | Creating checkout sessions and payment flows |
subscription-integration | Implementing subscription billing flows |
webhook-integration | Setting up and handling webhooks for payment events |
usage-based-billing | Implementing metered billing with events and meters |
credit-based-billing | Credit entitlements, balances, and metered credit deduction |
license-keys | Managing license keys for digital products |
billing-sdk | Using BillingSDK React components |
Skills source: dodopayments/skills (bundled as a git submodule in skills-src/).
Included MCP Servers
| Server | Purpose | Auth |
|---|---|---|
dodopayments-api | Live API access (payments, subscriptions, customers, products, refunds, licenses, usage) | OAuth (browser) |
dodo-knowledge | Semantic search over the Dodo Payments documentation | None |
Both servers are wired through mcp-remote so they run in any MCP-compatible client.
Configure (optional, Claude Code)
If you prefer to run the API MCP locally with an API key instead of the remote SSE server, open /plugins in Claude Code, select Dodo Payments, and choose Configure options. Fill in:
dodo_api_key- yourdodo_test_...ordodo_live_...keydodo_webhook_key- your webhook signing secretdodo_environment-test_modeorlive_mode
Then edit .mcp.json to point dodopayments-api at the local stdio server:
{
"mcpServers": {
"dodopayments-api": {
"type": "stdio",
"command": "npx",
"args": ["-y", "dodopayments-mcp@latest"],
"env": {
"DODO_PAYMENTS_API_KEY": "${user_config.dodo_api_key}",
"DODO_PAYMENTS_WEBHOOK_KEY": "${user_config.dodo_webhook_key}",
"DODO_PAYMENTS_ENVIRONMENT": "${user_config.dodo_environment}"
}
}
}
}
Run /reload-plugins to apply changes to your current session.
Enable / disable individual MCP servers
Both MCPs ship enabled by default. You can turn either one off independently.
OpenCode
The npm plugin reads two environment variables before registering MCPs:
| Env var | Effect |
|---|---|
DODO_DISABLE_API_MCP=1 | Skips registering dodopayments-api |
DODO_DISABLE_KNOWLEDGE_MCP=1 | Skips registering dodo-knowledge |
Truthy values: 1, true, yes, on (case-insensitive). Export the var in your shell profile or set it inline:
DODO_DISABLE_API_MCP=1 opencode
Claude Code, Codex CLI, Cursor
These clients load MCPs from the static .mcp.json shipped with the plugin. To disable a server, override its entry in your own project-level config and set "enabled": false.
Claude Code - edit .mcp.json at your project root (or run claude mcp disable dodopayments-api):
{
"mcpServers": {
"dodopayments-api": {
"type": "stdio",
"command": "npx",
"args": ["-y", "mcp-remote@latest", "https://mcp.dodopayments.com/sse"],
"enabled": false
}
}
}
Run /reload-plugins to apply.
Codex CLI / Cursor - the same enabled: false pattern works in any project-level .mcp.json that overrides the plugin's bundled file. Restart the client after editing.
Per-MCP toggles inside the Claude Code
/pluginUI are tracked upstream in anthropics/claude-code#27105 and #46373. Until those land, theenabled: falseoverride above is the supported path.
A prompt to try first
Once the plugin is active, try:
Set up Dodo Payments webhook handlers in my Next.js app for payment.succeeded and subscription.active events.
Your agent will load the webhook-integration skill, use the dodo-knowledge MCP to pull the latest payload shapes, and write a handler with signature verification following the Standard Webhooks spec.
Local development
Clone with the skills submodule:
git clone --recurse-submodules https://github.com/dodopayments/dodo-agent-plugin.git
cd dodo-agent-plugin
Validate the Claude Code plugin and marketplace:
claude plugin validate .
Load the plugin directly for a dev session:
claude --plugin-dir ./dodo-agent-plugin
Refresh the bundled skills to the latest upstream version:
git submodule update --remote skills-src
For maintainers
The repo is configured to publish the OpenCode npm package on every GitHub Release.
One-time setup (already done for this repo):
- npm scope
@dodopaymentsexists and is owned by Dodo Payments. - GitHub Actions secret
NPM_TOKENis provisioned with publish rights to the@dodopaymentsscope.
Release workflow:
- Bump the version in
.claude-plugin/plugin.json. - Run
node scripts/sync-manifests.mjsto propagate the version to Cursor, Codex, npm, and marketplace manifests. - Commit and tag.
- Create a GitHub Release - the
Publish @dodopayments/opencode-pluginworkflow runs automatically and publishes to npm with provenance.
Manual dry-run:
- Workflow dispatch with
dry_run: trueto validate the release pipeline without publishing.
CI check:
node scripts/sync-manifests.mjs --checkis run by the workflow and fails the release if any manifest is out of sync.
Resources
License
MIT - see LICENSE.
関連サーバー
Alpha Vantage MCP Server
スポンサーAccess financial market data: realtime & historical stock, ETF, options, forex, crypto, commodities, fundamentals, technical indicators, & more
Wazuh MCP Server
Integrates Wazuh security data with local LLM clients.
MCP Tools
Provides file system and command execution tools for LLM clients like Claude Desktop.
Yellhorn MCP
An MCP server that integrates Gemini 2.5 Pro and OpenAI models for software development tasks, allowing the use of your entire codebase as context.
Awesome LLMs Txt
Access documentation from the Awesome-llms-txt repository directly in your conversations.
Contentrain MCP
Extract, govern, and ship structured content from your codebase.
MCP Neurolora
An intelligent server for code analysis, collection, and documentation generation using the OpenAI API.
Claude Code Buddy (CCB)
Add persistent project memory and smart task routing to Claude Code. Stop repeating context every session - Claude finally remembers your architecture, decisions, and patterns forever. 100% local, 17 MCP tools.
Grafana
Access and manage Grafana resources, including dashboards, datasources, Prometheus, Loki, and alerting.
Claude KVM
🤖 ⚡️ MCP server ( MacOS) — control remote desktops via VNC
ocireg
An SSE-based MCP server that allows LLM-powered applications to interact with OCI registries. It provides tools for retrieving information about container images, listing tags, and more.