The official Dodo Payments plugin for AI coding agents. Installs the Dodo Payments integration skills and two MCP servers across , , , , , , , , , , and more, from a single source of truth.
Semantic search over the current Dodo Payments documentation. No authentication required.
2026-11-09
星數
—
工具
—
可用率
—
Claude Code
Codex CLI
Cursor
VS Code / GitHub Copilot
Grok Build
Meta Muse Code
Gemini CLI
Antigravity
Junie
OpenCode
This plugin conforms to the Agent Plugins 1.0.0 specification: a root plugin.json, skills as immediate children of skills/, and MCP servers in mcp.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.
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.
Agent skills - Integration guides (listed below), written as SKILL.md files 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
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
Register the marketplace, then install the plugin:
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: run codex, type /plugins, select the Dodo Payments marketplace and the dodopayments plugin, then choose Install plugin.
If you added the marketplace previously and the plugin doesn't appear, refresh it:
Restart Cursor. The plugin loads skills from skills/ 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 own name regex, and accepts either .cursor-plugin/marketplace.json or .claude-plugin/marketplace.json as a marketplace source. The generated .cursor-plugin/plugin.json is kept as belt-and-braces for older builds.
Prior to v0.5.0 this clone produced a plugin with no working skills: skills/ contained symlinks into a git submodule that a plain git clone does 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
Kiro reads the Agent Plugins manifest natively and loads this as a Power:
Point Kiro at the cloned folder. Skills load from skills/, MCP servers from mcp.json, and Kiro-specific presentation comes from the dev.kiro extension namespace in plugin.json.
gemini-extension.json at the repo root is the manifest, and Gemini auto-discovers the skills/ directory next to it. Verified on Gemini CLI 0.63.0: gemini skills list shows every skill and gemini mcp list shows both servers.
Then open the Chat view, go to Plugins, and add the cloned folder. Skills load from skills/, 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 root plugin.json, and defaults MCP to .mcp.json rather than mcp.json. Because this repo ships a generated .claude-plugin/plugin.json, VS Code loads it through that branch. Everything works - all skills and both MCP servers - via the compatibility manifests rather than the spec ones.
OpenCode
OpenCode distributes via npm. Add the plugin to your opencode.json:
Restart OpenCode. Both MCP servers (dodopayments-api, dodo-knowledge) are registered automatically via the plugin's config hook as native remote servers. No manual mcp block required. Run opencode mcp auth dodopayments-api to sign in to the API server.
Skills need the package installed locally plus one extra line. OpenCode does not scan installed packages for skills, so point it at the package's skills/ directory yourself. skills.paths entries resolve against the project directory, so the package must be present in the project's node_modules - OpenCode's own plugin cache is not the same location:
An absolute path works too, and avoids the local-install requirement.
Verify with opencode run "List every skill available to you by name." - you should see every skill listed under Included Skills. 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. Setting config.skills from the plugin's config hook does not fix this either - the skill index is built before config hooks 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, declare dodopayments-api yourself in opencode.json - your entry wins over the plugin default:
Refunds, disputes and chargebacks, access reconciliation
UI and integrations
Skill
Description
billing-sdk
BillingSDK React components for pricing tables and billing UI
better-auth-integration
The @dodopayments/better-auth plugin for customer sync, checkout, portal
Skills source: dodopayments/skills, vendored into skills/ as real files. Provenance (upstream commit and applied transforms) is recorded in .skills-source.json.
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 speak Streamable HTTP over HTTPS, and every manifest dials them natively - no npx mcp-remote bridge and no Node dependency. The canonical mcp.json uses the spec's type: "streamable-http"; the generated .mcp.json (Claude Code, Cursor, VS Code, Grok Build, Devin, Goose, Droid) uses the same endpoints spelled type: "http", the name that dialect uses; Muse, Antigravity, Junie and Gemini get their own spellings from the generator.
Configure (optional, Claude Code)
If you prefer to run the API MCP locally with an API key instead of the remote server, open /plugins in Claude Code, select Dodo Payments, and choose Configure options. Fill in:
dodo_api_key - your dodo_test_... or dodo_live_... key
dodo_webhook_key - your webhook signing secret
dodo_environment - test_mode or live_mode
Then edit .mcp.json to point dodopayments-api at the local stdio server:
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):
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 /plugin UI are tracked upstream in anthropics/claude-code#27105 and #46373. Until those land, the enabled: false override 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
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:
claude plugin validate .
Load the plugin directly for a dev session:
claude --plugin-dir ./dodo-agent-plugin
Verify everything before pushing:
npm run verify # generated artifacts in sync + Agent Plugins conformance
Repository layout
Path
Role
plugin.json
Canonical. Agent Plugins v1.0.0 manifest and the version source of truth
mcp.json
Canonical. Agent Plugins v1.0.0 MCP config
skills/
Canonical. Skills, vendored as real files; the declared set lives in .skills-source.json
overlays/*.json
Hand-authored provider extras the closed spec schema cannot express
Skills are authored in dodopayments/skills and vendored here. A weekly workflow re-syncs them and opens a PR; run it on demand with the Sync skills from upstream workflow dispatch.
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 @dodopayments exists and is owned by Dodo Payments.
npm Trusted Publishing (OIDC) is configured for @dodopayments/opencode-plugin against publish-opencode.yml. No npm token is stored in the repo.
Release workflow:
Bump version in plugin.json (the single source of truth).
Run npm run build to propagate it to every generated manifest.
Run npm run verify, then commit and tag.
Create a GitHub Release - the Publish @dodopayments/opencode-plugin workflow publishes to npm with provenance.
Manual dry-run:
Workflow dispatch with dry_run: true to validate the release pipeline without publishing.
CI checks:
Verify runs on every pull request and push to main: artifact drift, Agent Plugins conformance, live JSON Schema validation, an "every declared skill, zero symlinks" assertion, per-client manifest checks (Muse, Antigravity, Junie, Gemini), and an npm payload check.
The release workflow re-runs the same gates before publishing.