Dodo Payments skills and MCP server hints for OpenCode.
Connect Dodo Agent Plugin to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Dodo Payments skills and MCP server hints for OpenCode. The dodo agent plugin mcp server is what makes that connection.
The official Dodo Payments plugin for AI coding agents. Installs seventeen integration skills and two MCP servers across Claude Code, Codex CLI, Cursor, and OpenCode from a single source of truth.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
dodo_api_key — your dodo_test_... or dodo_live_... keydodo_webhook_key — your webhook signing secretdodo_environment — test_mode or live_modeSkill — Descriptionbest-practices — SDK setup, environments, API keys, and the canonical checkout-to-webhook architectureframework-adapters — Official @dodopayments/* handlers for Next.js, Express, Hono, Astro, Remix, SvelteKit, Nuxt, Fastify, TanStack, Bun, Convextesting-and-go-live — Test mode, test payment methods, webhook testing, production launch checklistcheckout-integration — Checkout Sessions, payment links, and overlay checkoutsubscription-integration — Subscription lifecycle, trials, plan changes, proration, on-demand chargesmobile-checkout — In-app checkout for React Native, Flutter, iOS, and Androidwebhook-integration — Receiving and verifying webhooks via the Standard Webhooks speccredit-based-billing — Credit entitlements, balances, ledger, rollover, overage, meter-based deductionConfiguration is passed through the environment: DODO_PAYMENTS_API_KEY, DODO_PAYMENTS_WEBHOOK_KEY, DODO_PAYMENTS_ENVIRONMENT. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
This sits in the payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Dodo Agent Plugin's toolset — dodo_api_key, dodo_webhook_key, dodo_environment and 11 more — is a fair guide to whether it matches your workflow. It is maintained by dodopayments; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Dodo Agent Plugin's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| dodo_api_key | your dodo_test_... or dodo_live_... key |
| dodo_webhook_key | your webhook signing secret |
| dodo_environment | test_mode or live_mode |
| Skill | Description |
| best-practices | SDK setup, environments, API keys, and the canonical checkout-to-webhook architecture |
| framework-adapters | Official @dodopayments/* handlers for Next.js, Express, Hono, Astro, Remix, SvelteKit, Nuxt, Fastify, TanStack, Bun, Convex |
| testing-and-go-live | Test mode, test payment methods, webhook testing, production launch checklist |
| checkout-integration | Checkout Sessions, payment links, and overlay checkout |
| subscription-integration | Subscription lifecycle, trials, plan changes, proration, on-demand charges |
| mobile-checkout | In-app checkout for React Native, Flutter, iOS, and Android |
| webhook-integration | Receiving and verifying webhooks via the Standard Webhooks spec |
| credit-based-billing | Credit entitlements, balances, ledger, rollover, overage, meter-based deduction |
| usage-based-billing | Meters, event ingestion, aggregation, and per-unit pricing |
| license-keys | License key activation, validation, and instance management |
{
"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}"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DODO_PAYMENTS_API_KEY | Credential the server authenticates with. | Yes |
| DODO_PAYMENTS_WEBHOOK_KEY | Credential the server authenticates with. | Yes |
| DODO_PAYMENTS_ENVIRONMENT | Configuration value read at startup. | Optional |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.