Stripe MCP
Official Stripe MCP server and agent toolkit for working with Stripe customers, payments, subscriptions, refunds, invoices, and billing operations.Read full description
stripeLABSCO SUMMARY
Two tools instead of a hundred, because the agent writes the script.
Code Mode gives the agent a documentation search and a sandbox: listing active subscriptions, filtering them and applying a discount to each is one invocation rather than a chain of endpoint calls. The knowledge server is worth adding alongside it — it answers how to implement something from current docs before any code runs.
What it is
The official Dodo Payments plugin for AI coding agents, built to the Agent Plugins 1.0.0 specification. It registers two MCP servers and a skill library across Claude Code, Codex CLI, Cursor, VS Code, Kiro and OpenCode from a single source.
What you get
- The Dodo Payments API server, which works in Code Mode: two tools rather than one per endpoint — a documentation search, and a code execution tool that runs TypeScript against the SDK in an isolated sandbox
- The Dodo Knowledge server: semantic search over current Dodo Payments documentation, with no credentials
- Seventeen skills the agent loads on its own, including checkout-integration, subscription-integration, mobile-checkout, webhook-integration, credit-based-billing, usage-based-billing, license-keys, framework-adapters, testing-and-go-live and dodo-best-practices
- API coverage through the sandbox: payments and refunds, subscriptions, customers and portal access, products, pricing and discounts, license activation and validation, and metered usage
- Framework handlers for Next.js, Express, Hono, Astro, Remix, SvelteKit, Nuxt, Fastify, TanStack, Bun and Convex
Requirements
Node.js 18 or higher. On Claude Code, claude plugins marketplace add dodopayments/dodo-agent-plugin then claude plugins install dodopayments@dodopayments; Codex, Cursor, Kiro, VS Code and OpenCode each have their own path. The API server uses browser OAuth, so there is no key at install time — you sign in the first time the agent calls a Dodo tool. Gemini CLI gets the two servers but not the skills, having no skill primitive. A local stdio alternative takes DODO_PAYMENTS_API_KEY, DODO_PAYMENTS_WEBHOOK_KEY and DODO_PAYMENTS_ENVIRONMENT instead.
Setup effort
One command, then sign in — claude plugins marketplace add dodopayments/dodo-agent-plugin && claude plugins install dodopayments@dodopayments, then approve the OAuth sign-in
USE CASES
01
Wiring checkout into an app
The agent loads the checkout skill on its own, then uses the framework handler for your stack rather than inventing the integration.
02
Doing something across many subscriptions at once
List, filter and act in a single sandboxed script, instead of one endpoint call per model turn.
03
Getting webhooks right
Search the current documentation for the verification contract before writing the handler, since this is where signature checks usually go wrong.
04
Preparing to go live
The testing-and-go-live skill covers test mode, test payment methods, webhook testing and the production checklist as a sequence rather than scattered docs.
BEFORE YOU INSTALL
What to know first
Requires
A Dodo Payments account, signed in over browser OAuth the first time your agent calls a Dodo tool
Optional
DODO_PAYMENTS_API_KEY in your environment
INSTALLATION
Connect your client
Server setup
The command line the project publishes
Claude Code
TERMINAL
claude plugins marketplace add dodopayments/dodo-agent-plugin
claude plugins install dodopayments@dodopaymentsHosted endpoint
ENDPOINT URL
https://mcp.dodopayments.com/sseAdd this hosted endpoint to your MCP client, then sign in.
MCP Clients
Codex
CODEX · TERMINAL
codex plugin marketplace add dodopayments/dodo-agent-plugin
codex plugin add dodopayments@dodopaymentsCursor
CURSOR · TERMINAL
git clone https://github.com/dodopayments/dodo-agent-plugin.git ~/.cursor/plugins/local/dodo-agent-pluginKiro
Clone the plugin repository:
KIRO · TERMINAL
git clone https://github.com/dodopayments/dodo-agent-plugin.gitPoint Kiro at the cloned folder. Kiro reads the Agent Plugins manifest natively and loads it as a Power: skills from skills/, MCP servers from mcp.json.
Gemini CLI
GEMINI CLI · TERMINAL
git clone https://github.com/dodopayments/dodo-agent-plugin.git \
~/.gemini/extensions/dodopaymentsGitHub Copilot in VS Code
Clone the repository anywhere:
GITHUB COPILOT IN VS CODE · TERMINAL
git clone https://github.com/dodopayments/dodo-agent-plugin.gitOpen the Chat view, go to Plugins, and add the cloned folder — or register it in settings.json, with the key set to your clone's path (absolute or ~/):
GITHUB COPILOT IN VS CODE · JSON
{
"chat.pluginLocations": {
"~/dodo-agent-plugin": true
}
}~/dodo-agent-plugin is the path when you cloned into your home folder; use the path of your own clone.
OpenCode
OPENCODE · JSON
{
"$schema": "https://opencode.ai/config.json",
"plugin": [
"@dodopayments/opencode-plugin"
],
"skills": {
"paths": [
"node_modules/@dodopayments/opencode-plugin/skills"
]
}
}Claude Desktop, Windsurf
JSON
{
"mcpServers": {
"dodopayments": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"https://mcp.dodopayments.com/sse"
]
}
}
}VS Code — Cline
VS CODE — CLINE · JSON
{
"servers": {
"dodopayments": {
"command": "npx",
"args": [
"-y",
"dodopayments-mcp@latest"
],
"env": {
"DODO_PAYMENTS_API_KEY": "<YOUR_DODO_PAYMENTS_API_KEY>",
"DODO_PAYMENTS_WEBHOOK_KEY": "<YOUR_DODO_PAYMENTS_WEBHOOK_KEY>"
}
}
}
}This entry runs the local dodopayments-mcp server with an API key instead of the OAuth sign-in: <YOUR_DODO_PAYMENTS_API_KEY> is your API key (it starts with dodo_test_ or dodo_live_), and <YOUR_DODO_PAYMENTS_WEBHOOK_KEY> your webhook signing key, which is optional. For live_mode keys, also add "DODO_PAYMENTS_ENVIRONMENT": "live_mode" to env. Reload the VS Code window afterwards.
Any MCP client — Dodo Knowledge
ANY MCP CLIENT — DODO KNOWLEDGE · JSON
{
"mcpServers": {
"dodo-knowledge": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"https://knowledge.dodopayments.com/mcp"
]
}
}
}
