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
Register the marketplace, then install the plugin:
codex plugin marketplace add dodopayments/dodo-agent-plugin
codex plugin add dodopayments@dodopayments
Verify:
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:
codex plugin marketplace upgrade dodopayments
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 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:
git clone https://github.com/dodopayments/dodo-agent-plugin.git
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 CLI (MCP only)
Gemini CLI has no agent-skill primitive, so only the two MCP servers are available - the seventeen skills are not. dodo-knowledge still 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.json at the repo root is the manifest.
VS Code / GitHub Copilot
git clone https://github.com/dodopayments/dodo-agent-plugin.git
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 - seventeen skills and two MCP servers - but via the compatibility manifests rather than the spec ones, so VS Code gets the mcp-remote bridge rather than the native transports in 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. No manual mcp block 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'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:
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 with opencode 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. 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:
{
"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
}
}
}
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_... keydodo_webhook_key - your webhook signing secretdodo_environment - test_mode or live_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.