Dodo Payments Agent Plugin
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
The official Dodo Payments plugin for AI coding agents. Installs the Dodo Payments integration skills and two MCP servers 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 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.
Install
| Client | Skills | MCP | How |
|---|---|---|---|
| Claude Code | ✅ | ✅ | Marketplace |
| Codex CLI / ChatGPT | ✅ | ✅ | Marketplace |
| Cursor (and Grok Bot) | ✅ | ✅ | Clone |
| VS Code / GitHub Copilot | ✅ | ✅ | Plugins view · Copilot CLI |
| Grok Build | ✅ | ✅ | grok plugin install |
| grok.com, xAI API | — | ✅ | Connector / API tool |
| Meta Muse Code | ✅ | ✅ | muse plugins install |
| Gemini CLI | ✅ | ✅ | Extension |
| Google Antigravity | ✅ | ✅ | agy plugin install |
| JetBrains Junie | ✅ | ✅ | Extension |
| Kiro | ✅ | ✅ | Power |
| OpenCode | ✅ | ✅ | npm |
| Qwen Code, Devin, Goose, Factory Droid, Augment, OpenHands, OpenClaw, Hermes | ✅ | ✅ | More clients |
| Cline, Kilo, Zed, Warp, Amp, Continue, Kimi, … | ✅ | ✅ | npx skills + npx add-mcp |
| Claude.ai, ChatGPT, Perplexity, Mistral | — | ✅ | Custom connector |
Claude Code
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:
Verify:
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:
Cursor
Manual install:
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 CLI
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.
VS Code / GitHub Copilot
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.