Dodo Payments

Dodo Payments Agent Plugin

The official Dodo Payments plugin for AI coding agents. Installs the Dodo Payments integration skill and MCP server across Claude Code, Codex CLI, Cursor, VS Code / GitHub Copilot, Grok Build, Meta Muse Code, Gemini CLI, Antigravity, Junie, OpenCode, and more, from a single source of truth.

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 MCP server (dodopayments) - Documentation search plus live API access (payments, subscriptions, customers, products, refunds, licenses, usage). Authenticates via browser OAuth, no local credentials required.
• Agent skill - One dodo-payments skill (listed below), written as a SKILL.md index with reference files your agent loads on demand when a task calls for them.

Install

Claude Code

claude plugins marketplace add dodopayments/dodo-agent-plugin

claude plugins install dodopayments@dodopayments

The MCP server signs in with OAuth, so there is no API key to paste. Your client starts the sign-in when the server is added or connected (run /mcp if it doesn't), and a Dodo Payments consent page opens in your browser: pick the business, mode and permissions. See Sign-in and access.

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 # dodopayments codex mcp login dodopayments # browser OAuth

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

gemini extensions install https://github.com/dodopayments/dodo-agent-plugin

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 the skill and gemini mcp list shows the server.

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 the MCP server loads 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, the skill and the MCP server, via the compatibility manifests rather than the spec ones.

OpenCode

OpenCode distributes via npm. Add the plugin to your opencode.json:

{

"$schema": "https://opencode.ai/config.json", "plugin": ["@dodopayments/opencode-plugin"] }

Restart OpenCode. The MCP server (dodopayments) is registered automatically via the plugin's config hook as a native remote server. No manual mcp block required. Run opencode mcp auth dodopayments to open the Dodo Payments consent page.

The skill needs 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 dodo-payments (see Included Skill). A skills path that does not exist is ignored silently, so check rather than assume.

Versions before 0.5.0 documented the skills as auto-discovered. They were not: nothing in OpenCode scans an installed package, so OpenCode users had the 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.

Included Skill

One skill, dodo-payments. Its SKILL.md is a short index; the details live in reference files that your agent loads only when the task needs them.

Skill source: dodopayments/skills (dodo-payments/dodo-payments), vendored into skills/ as real files. Provenance (upstream commit and applied transforms) is recorded in .skills-source.json.

Included MCP Server

Tools:

The server speaks Streamable HTTP over HTTPS, and every manifest dials it 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 endpoint spelled type: "http", the name that dialect uses; Muse, Antigravity, Junie and Gemini get their own spellings from the generator.

Sign-in and access

The MCP server signs in with OAuth. No config in this plugin holds an API key, and no step asks you to paste one.

1. The server returns 401 until the client signs in, so the client starts OAuth when the server is added or connected and opens a Dodo Payments consent page in your browser. Some clients start it from a command: /mcp in Claude Code, codex mcp login dodopayments, opencode mcp auth dodopayments, muse mcp login dodopayments, or devin mcp login dodopayments.
2. Sign in, then pick the business, the mode (test or live) and the permissions to grant.
3. The client stor