dodo-agent-plugin

Purpose

The Dodo Payments Agent Plugin is an AI coding agent plugin officially released by Dodo Payments. Its goal is to provide Dodo Payments integration capabilities for various AI coding agents, enabling agents to directly call the Dodo Payments payment API, search official documentation, and load the corresponding integration skills when needed. It follows the Agent Plugins 1.0.0 specification and uses a single source (root plugin.json, skills/, mcp.json) to generate client-compatible manifests.

Main capabilities

MCP servers

• Dodo Payments API MCP server: provides real-time API access, covering payments, subscriptions, customers, products, refunds, licenses, usage. By default, it uses browser OAuth authentication, so no local credentials are required during installation; the first time a Dodo tool is called, it will prompt for login.
• Dodo Knowledge MCP server: requires no credentials and performs semantic search over the current Dodo Payments documentation. Both servers use Streamable HTTP over HTTPS, with each manifest dialing natively, without an npx mcp-remote bridge and without Node dependencies. The canonical mcp.json uses type: "streamable-http"; the generated .mcp.json (used for Claude Code, Cursor, VS Code, Grok Build, Devin, Goose, Droid) uses the same endpoint but spells it as type: "http"; Muse, Antigravity, Junie, and Gemini use their own spellings.

Agent skills

Skills are provided as SKILL.md files (with YAML frontmatter), and agents will load the relevant skills themselves when a task requires them. Included skill topics:

• Getting started
• Accepting payments
• Catalog and pricing
• Customers and operations
• UI and integrations Skills originate from dodopayments/skills and are vendored as real files into the skills/ directory, with the source recorded in .skills-source.json.

Usage

Installation (per client)

• General: register the marketplace and then install the plugin.
• Codex CLI: run codex in the TUI, type /plugins, select the Dodo Payments marketplace and the dodopayments plugin, then select Install plugin. If the marketplace has already been added but the plugin does not appear, you can refresh.
• Manual installation: clone the repository.
• Cursor: 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 directly recognizes Agent Plugins 1.0.0.
• Kiro: natively reads the Agent Plugins manifest and loads it as a Power; just point it to the cloned folder.
• Gemini CLI: gemini-extension.json serves as the manifest in the repository root, and Gemini automatically discovers the adjacent skills/ directory. Verified on Gemini CLI 0.63.0: gemini skills list shows all skills, and gemini mcp list shows both servers.
• VS Code / GitHub Copilot: open the Chat view, go to Plugins, and add the cloned folder. Skills are loaded from skills/, and the two MCP servers are loaded from .mcp.json.
• OpenCode: distributed via npm. Add the plugin to opencode.json and restart OpenCode; the two MCP servers (dodopayments-api, dodo-knowledge) will automatically register as native remote servers. Run opencode mcp auth dodopayments-api to log in to the API server. Skills require a local installation package and additional configuration skills.paths points to the package's skills/ directory (resolved relative to the project directory, so the package must exist in the project's node_modules; an absolute path may also be used).

Optional configuration (Claude Code)

If you want to use a local stdio API server and your own API key instead of the default remote OAuth server, open /plugins in Claude Code, select Dodo Payments, select Configure options, and fill in:

• dodo_api_key: dodo_test_... or dodo_live_...
• dodo_webhook_key: webhook signing secret
• dodo_environment: test_mode or live_mode Then edit .mcp.json to point dodopayments-api to the local stdio server, and run /reload-plugins to apply.

Enabling/disabling MCP servers

Both MCPs are enabled by default and can be disabled independently. The npm plugin reads two environment variables before registering the MCPs. Truthy values: 1, true, yes, on (case-insensitive). Claude Code, Codex CLI, and Cursor load MCPs from the static .mcp.json; to disable, override the corresponding entry in the project-level configuration and set "enabled": false; in Claude Code you can run claude mcp disable dodopayments-api, then /reload-plugins.

Try an example

After the plugin is activated, you can try having the agent load the webhook-integration skill, use the dodo-knowledge MCP to get the latest payload shape, and write a handler with signature verification according to the Standard Webhooks specification.

When to use

• Integrate Dodo Payments payments, subscriptions, refunds, licenses, and usage-based billing in AI coding agents.
• Quickly look up Dodo Payments documentation via semantic search.
• When you need the agent to automatically load payment-related skills and generate integration code.

Limitations

• Skills requirean OpenCode local installation package and additional configuration, and if no skills path exists it will be silently ignored.
• VS Code 1.125.1 does not load based on Agent Plugins $schema, but via a compatibility manifest; MCP uses .mcp.json by default instead of mcp.json.
• Clones with versions below v0.5.0 will produce non-working skills (skills/ is a symlink pointing to a submodule), so you need to re-clone.
• Toggling features by MCP in Claude Code's /plugin UI is not yet supported upstream.

Development and license

The repository has no submodules and no build step; skills are vendored as real files. Validation, loading, and release processes are provided. The license is MIT.