# dodopayments/dodo-agent-plugin [Verified] [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/dodopayments/dodo-agent-plugin  
**GitHub Stars:** 6  
**npm Downloads (last month):** 3611  
**Views:** 7  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/dodopayments-dodo-agent-plugin

## Description
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.

## Tools
Capabilities this server exposes over MCP:

- **execute** — Runs JavaScript code to interact with the Dodo Payments API.

You are a skilled TypeScript programmer writing code to interface with the service.
Define an async function named "run" that takes a single parameter of an initialized SDK client and it will be run.
For example:

```
async function run(client) {
  const checkoutSessionResponse = await client.checkoutSessions.create({ product_cart: [{ product_id: 'pdt_example', quantity: 1 }] });

  console.log(checkoutSessionResponse.session_id);
}
```

You will be returned anything that your function returns, plus the results of any console.log statements.
Do not add try-catch blocks for single API calls. The tool will handle errors for you.
Do not add comments unless necessary for generating better code.
Code will run in a container, and cannot interact with the network outside of the given SDK client.
Variables will not persist between calls, so make sure to return or log any data you might need later.
Remember that you are writing TypeScript code, so you need to be careful with your types.
Always type dynamic key-value stores explicitly as Record<string, YourValueType> instead of {}.
- **search_docs** — Search SDK documentation to find methods, parameters, and usage examples for interacting with the API. Use this before writing code when you need to discover the right approach.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "dodo-agent-plugin": {
    "command": "npx",
    "args": ["-y","dodopayments-mcp@latest"]
  }
}
```

## Documentation

## What dodopayments/dodo-agent-plugin MCP server does

The dodopayments/dodo-agent-plugin MCP server distributes two MCP servers alongside a collection of agent skills. `dodopayments-api` provides live access to Dodo Payments functionality, including payments, subscriptions, customers, products, refunds, license keys, and usage-based billing. `dodo-knowledge` performs semantic search across the current Dodo Payments documentation and does not require credentials.

The package is intended for AI coding agents rather than as a standalone payments SDK. The repository follows the Agent Plugins 1.0.0 layout, with MCP definitions in `mcp.json`, skills under `skills/`, and compatibility manifests for clients that do not load the standard format directly.

## How it works

The API MCP server uses browser OAuth by default. No local API key is needed for the standard setup; the first request to a Dodo tool prompts the user to sign in. The documentation server is available without authentication.

The plugin can load in Claude Code, Codex CLI, Cursor, Kiro, Gemini CLI, VS Code with GitHub Copilot, and OpenCode, although the exact installation and feature coverage differ. Gemini CLI receives the two MCP servers but not the seventeen skills. OpenCode registers both MCP servers through its plugin configuration, while its skills require a locally installed package and an explicit `skills.paths` entry.

## Setup and configuration

Installation is client-specific. Claude Code and Codex CLI install the repository through their plugin marketplace commands. Cursor, Kiro, Gemini CLI, and VS Code use a cloned repository directory. OpenCode uses the `@dodopayments/opencode-plugin` npm package in `opencode.json`.

For OpenCode, the plugin is sufficient to register both MCP servers. To expose the bundled skills, install the package in the project and point `skills.paths` to its `node_modules/@dodopayments/opencode-plugin/skills` directory. OpenCode can also override the default remote API server with a local `dodopayments-mcp@latest` entry using `DODO_PAYMENTS_API_KEY`, `DODO_PAYMENTS_WEBHOOK_KEY`, and `DODO_PAYMENTS_ENVIRONMENT`.

## Tools and capabilities

The dodopayments/dodo-agent-plugin MCP server supports live payment administration and documentation lookup. The included skills provide written guidance for SDK setup, environments, checkout sessions, payment links, subscriptions, mobile checkout, webhook verification, credit billing, usage billing, and license keys. Additional catalog and pricing skills are included in the repository, for a total of seventeen skills.

## Limitations and notes

Capabilities depend on the host client. Gemini CLI exposes MCP only, and OpenCode does not discover installed-package skills automatically. Older versions of the repository had an OpenCode skill-discovery issue; the documented local package and `skills.paths` configuration is required for current use. Browser OAuth applies to the default API server, while a local API configuration requires the user’s Dodo credentials.

_Full upstream README: https://allmcps.com/mcp/dodopayments-dodo-agent-plugin/readme_