Dodo Payments
About
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.
Details
- Author
- dodopayments
- Categories
- Finance, Other, API
Jump to
Setup
Install Dodo Payments in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/dodopayments/dodo-agent-plugin
Follow the installation instructions in the repository README, then restart your MCP client.
The official Dodo Payments plugin for AI coding agents. Installs seventeen integration skills and two MCP servers acrossClaude Code,Codex CLI,Cursor,VS Code / GitHub Copilot, andOpenCodefrom a single source of truth.
This plugin conforms to theAgent Plugins 1.0.0specification: a rootplugin.json, skills as immediate children ofskills/, and MCP servers inmcp.json. Clients with native Agent Plugins support load it directly; the provider-specific manifests in this repo are generated compatibility shims for clients that do not.
- 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.
- Seventeen agent skills- Written asSKILL.mdfiles with YAML frontmatter. Your agent loads the relevant skill on its own when a task calls for it.
claude plugins marketplace add dodopayments/dodo-agent-plugin claude plugins install dodopayments@dodopayments
Register the marketplace, then install the plugin:
codex plugin marketplace add dodopayments/dodo-agent-plugin codex plugin add dodopayments@dodopayments
codex plugin list # dodopayments installed, enabled codex mcp list # dodo-knowledge, dodopayments-api codex mcp login dodopayments-api # browser OAuth, only needed for the API server
You can also install from inside the TUI: runcodex, type/plugins, select theDodo Paymentsmarketplace and thedodopaymentsplugin, then chooseInstall plugin.
If you added the marketplace previously and the plugin doesn't appear, refresh it:
codex plugin marketplace upgrade dodopayments
git clone https://github.com/dodopayments/dodo-agent-plugin.git ~/.cursor/plugins/local/dodo-agent-plugin
Restart Cursor. The plugin loads skills fromskills/and MCP servers from.mcp.json, as declared in.cursor-plugin/plugin.json.
Cursor 3.14.27 also recognises Agent Plugins 1.0.0 directly: its agent host carries both spec schema URLs and the spec's ownnameregex, and accepts either.cursor-plugin/marketplace.jsonor.claude-plugin/marketplace.jsonas a marketplace source. The generated.cursor-plugin/plugin.jsonis kept as belt-and-braces for older builds.
Prior to v0.5.0 this clone produced a plugin withno working skills:skills/contained symlinks into a git submodule that a plaingit clonedoes not fetch. Skills are now vendored as real files, so the command above works as documented. If you installed an earlier version, re-clone.
Kiro reads the Agent Plugins manifest natively and loads this as a Power:
git clone https://github.com/dodopayments/dodo-agent-plugin.git
Point Kiro at the cloned folder. Skills load fromskills/, MCP servers frommcp.json, and Kiro-specific presentation comes from thedev.kiroextension namespace inplugin.json.
Gemini CLI has no agent-skill primitive, soonly the two MCP servers are available- the seventeen skills are not.dodo-knowledgestill covers a good share of what the skills provide, and it stays current automatically.
git clone https://github.com/dodopayments/dodo-agent-plugin.git \ ~/.gemini/extensions/dodopayments
Restart Gemini CLI.gemini-extension.jsonat the repo root is the manifest.
git clone https://github.com/dodopayments/dodo-agent-plugin.git
Then open the Chat view, go toPlugins, and add the cloned folder. Skills load fromskills/, and both MCP servers load from.mcp.json.
VS Code 1.125.1 does not key off the Agent Plugins$schema- the string appears nowhere in its bundle. Its loader picks a manifest by probing, in order,.plugin/plugin.json, then.claude-plugin/plugin.json, then a rootplugin.json, and defaults MCP to.mcp.jsonrather thanmcp.json. Because this repo ships a generated.claude-plugin/plugin.json, VS Code loads it through that branch. Everything works - seventeen skills and two MCP servers - but via the compatibility manifests rather than the spec ones, so VS Code gets themcp-remotebridge rather than the native transports inmcp.json.
OpenCode distributes via npm. Add the plugin to youropencode.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'sconfighook. No manualmcpblock required.
Skills need the package installed locally plus one extra line.OpenCode does not scan installed packages for skills, so point it at the package'sskills/directory yourself.skills.pathsentries resolve against the project directory, so the package must be present in the project'snode_modules- OpenCode's own plugin cache is not the same location:
npm install --save-dev @dodopayments/opencode-plugin
{ "$schema": "https://opencode.ai/config.json", "plugin": ["@dodopayments/opencode-plugin"], "skills": { "paths": ["node_modules/@dodopayments/opencode-plugin/skills"] } }
An absolute path works too, and avoids the local-install requirement.
Verify withopencode run "List every skill available to you by name."- you should see all seventeen. A skills path that does not exist is ignored silently, so check rather than assume.
Versions before 0.5.0 documented these skills as auto-discovered. They were not: nothing in OpenCode scans an installed package, so OpenCode users had MCP servers but no skills. Settingconfig.skillsfrom the plugin'sconfighook does not fix this either - the skill index is built beforeconfighooks run, so it never registers anything.
If you prefer the local stdio API server with your own API key instead of the default remote OAuth server, declaredodopayments-apiyourself inopencode.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 } } }
Skills source:dodopayments/skills, vendored intoskills/as real files. Provenance (upstream commit and applied transforms) is recorded in.skills-source.json.
Both servers speak Streamable HTTP. The canonicalmcp.jsondeclares them natively (type: "streamable-http"), which is what spec-native clients such as Codex CLI and Cursor use. The generated compatibility manifests —.mcp.json, read by Claude Code, VS Code and Cursor's legacy path — wire the same two endpoints throughmcp-remoteinstead, so they run in clients that cannot yet dial Streamable HTTP directly.
If you prefer to run the API MCP locally with an API key instead of the remote server, open/pluginsin Claude Code, selectDodo Payments, and chooseConfigure options. Fill in:
- dodo_api_key- yourdodo_test_...ordodo_live_...key
- dodo_webhook_key- your webhook signing secret
- dodo_environment-test_modeorlive_mode
Then edit.mcp.jsonto pointdodopayments-apiat 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-pluginsto apply changes to your current session.
Both MCPs ship enabled by default. You can turn either one off independently.
The npm plugin reads two environment variables before registering MCPs:
Truthy values:1,true,yes,on(case-insensitive). Export the var in your shell profile or set it inline:
These clients load MCPs from the static.mcp.jsonshipped with the plugin. To disable a server, override its entry in your own project-level config and set"enabled": false.
Claude Code- edit.mcp.jsonat your project root (or runclaude mcp disable dodopayments-api):
{ "mcpServers": { "dodopayments-api": { "type": "stdio", "command": "npx", "args": ["-y", "mcp-remote@latest", "https://mcp.dodopayments.com/mcp"], "enabled": false } } }
Codex CLI / Cursor- the sameenabled: falsepattern works in any project-level.mcp.jsonthat overrides the plugin's bundled file. Restart the client after editing.
Per-MCP toggles inside the Claude Code/pluginUI are tracked upstream inanthropics/claude-code#27105and#46373. Until those land, theenabled: falseoverride above is the supported path.
Set up Dodo Payments webhook handlers in my Next.js app for payment.succeeded and subscription.active events.
Your agent will load thewebhook-integrationskill, use thedodo-knowledgeMCP to pull the latest payload shapes, and write a handler with signature verification following the Standard Webhooks spec.
git clone https://github.com/dodopayments/dodo-agent-plugin.git cd dodo-agent-plugin
No submodules, no build step -skills/is vendored as real files.
Validate the Claude Code plugin and marketplace:
Load the plugin directly for a dev session:
npm run verify # generated artifacts in sync + Agent Plugins conformance
Skills are authored indodopayments/skillsand vendored here. A weekly workflow re-syncs them and opens a PR; run it on demand with theSync skills from upstreamworkflow dispatch.
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 secretNPM_TOKENis provisioned with publish rights to the@dodopaymentsscope.
- Bumpversioninplugin.json(the single source of truth).
- Runnpm run buildto propagate it to every generated manifest.
- Runnpm run verify, then commit and tag.
- Create a GitHub Release - thePublish @dodopayments/opencode-pluginworkflow publishes to npm with provenance.
- Workflow dispatch withdry_run: trueto validate the release pipeline without publishing.
- Verifyruns on every pull request and push tomain: artifact drift, Agent Plugins conformance, live JSON Schema validation, a "seventeen skills, zero symlinks" assertion, and an npm payload check.
- The release workflow re-runs the same gates before publishing.
- Dodo Payments documentation
- Agent Skills docs
- MCP Server docs
- Skills source repo
- Discord community
QuickBooks integration using OAuth2. Write operations disabled by default per integration. 550+ tools covering invoices, bills, reports, and inventory. Requires a DataGrout account.
Remote MCP server (Streamable HTTP, read-only, no auth) at https://doc.2328.io/mcp — integration documentation for the 2328 payment platform.
Secure agent purchasing with human-approved virtual cards.
AI intelligence oracle + cross-border settlement rail. 10-layer Stability Oracle (climate, macro, FX, ESG) with x402 pay-per-call API. USDC/EURC settlement on Base at 1.385% all-in.
A first-party PHP/Laravel Composer package that exposes QuickBooks Online (QBO) as a Model Context Protocol (MCP) server.
The Company Formation MCP for AI tools — form companies, manage bank accounts, cards, invoices and payments directly from your AI agent.
An MCP server that lets an agent autonomously pay any x402 (HTTP 402) API across 29 chains — budget-capped, self-custody, no facilitator or fee.
Script Master Labs Federal, Medical & Finance MCP (x402)
MCP server enabling AI agents to query institutional financial data APIs using x402 payment protocol for autonomous machine-to-machine commerce.
Remote MCP for paid API discovery, API invocation, USDC agent payments, and receipts.
One x402/developer-credit control layer for paid AI/data tool calls, crypto conversion quotes, public MCP discovery, progress streaming, and receipt-backed agent spend governance.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
