Dodo Payments Agent Plugin

Dodo Payments Agent Plugin

Official Dodo Payments MCP servers - dodopayments-api for live payments, subscriptions, customers, products, refunds, license keys, and usage-based billing (browser OAuth, no API key needed) and dodo-knowledge for semantic search over Dodo Payments documentation.

Category
访问服务器

README

Dodo Payments Agent Plugin

License Version npm Discord

The official Dodo Payments plugin for AI coding agents. Installs eight integration skills and two MCP servers across Claude Code, Codex CLI, Cursor, and OpenCode from a single source of truth.

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.
  • Eight agent skills - Written as SKILL.md files with YAML frontmatter. Your agent loads the relevant skill on its own when a task calls for it.

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

Codex installs plugins in two steps: register the marketplace from your shell, then install the plugin from inside the Codex TUI.

  1. Register the marketplace:

    codex plugin marketplace add dodopayments/dodo-agent-plugin
    
  2. Open Codex and run the /plugins slash command:

    codex
    

    Then type /plugins, switch to the Dodo Payments marketplace, select the dodopayments plugin, and choose Install plugin.

If you previously added the marketplace before this fix landed and the plugin doesn't appear under /plugins, refresh it:

codex plugin marketplace upgrade dodopayments

Codex CLI does not have a codex plugin install subcommand. Plugin installation always happens through the in-TUI /plugins flow (official docs).

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 .claude/skills/ (via Cursor's Claude Code compat) and MCP servers from .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, and the eight skills are auto-discovered from the installed package. No manual mcp block required.

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
        }
    }
}

Included Skills

Skill Description
best-practices Comprehensive guide to integrating Dodo Payments with best practices
checkout-integration Creating checkout sessions and payment flows
subscription-integration Implementing subscription billing flows
webhook-integration Setting up and handling webhooks for payment events
usage-based-billing Implementing metered billing with events and meters
credit-based-billing Credit entitlements, balances, and metered credit deduction
license-keys Managing license keys for digital products
billing-sdk Using BillingSDK React components

Skills source: dodopayments/skills (bundled as a git submodule in skills-src/).

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 are wired through mcp-remote so they run in any MCP-compatible client.

Configure (optional, Claude Code)

If you prefer to run the API MCP locally with an API key instead of the remote SSE 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:

{
    "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.

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):

{
    "mcpServers": {
        "dodopayments-api": {
            "type": "stdio",
            "command": "npx",
            "args": ["-y", "mcp-remote@latest", "https://mcp.dodopayments.com/sse"],
            "enabled": false
        }
    }
}

Run /reload-plugins to apply.

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

Clone with the skills submodule:

git clone --recurse-submodules https://github.com/dodopayments/dodo-agent-plugin.git
cd dodo-agent-plugin

Validate the Claude Code plugin and marketplace:

claude plugin validate .

Load the plugin directly for a dev session:

claude --plugin-dir ./dodo-agent-plugin

Refresh the bundled skills to the latest upstream version:

git submodule update --remote skills-src

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.
  • GitHub Actions secret NPM_TOKEN is provisioned with publish rights to the @dodopayments scope.

Release workflow:

  1. Bump the version in .claude-plugin/plugin.json.
  2. Run node scripts/sync-manifests.mjs to propagate the version to Cursor, Codex, npm, and marketplace manifests.
  3. Commit and tag.
  4. Create a GitHub Release - the Publish @dodopayments/opencode-plugin workflow runs automatically and publishes to npm with provenance.

Manual dry-run:

  • Workflow dispatch with dry_run: true to validate the release pipeline without publishing.

CI check:

  • node scripts/sync-manifests.mjs --check is run by the workflow and fails the release if any manifest is out of sync.

Resources

License

MIT - see LICENSE.

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选