Install dodopayments-mcp from npm
Install exact version 2.49.0. No verified executable entrypoint is available, so use the package documentation to launch it.
npm install --save-exact dodopayments-mcp@2.49.0MCP server intelligence profile
Dodo Payments MCP Server
The Dodo Payments MCP Server integrates with agentic frameworks to provide a lightweight, serverless-compatible interface for AI-driven payment operations like billing, subscriptions, and customer management.
1Distribution channel
2Independently observed tools
0Linked remote endpoints
AvailableVersion intelligence
Install and connect
Installation and connection instructions are shown only when supported by retained package, repository, or endpoint evidence.
Identity
| Canonical slug | dodo-payments-0909744e | Deployment | Local Only |
|---|---|---|---|
| Canonical package | npm:dodopayments-mcp | Repository | dodopayments/dodopayments-typescript |
| First published | Aug 7, 2026 | Latest release | Aug 7, 2026 |
| Last security verification | Sep 1, 2026 | Classification confidence | 90% |
| Publication | Published | Official distribution | Yes |
Distributions
| Channel | Identifier | Current version | Versions | Source |
|---|---|---|---|---|
| npm | dodopayments-mcp | 2.49.0 | 137 | Repository |
Current release
| Package | Version | Published / observed | Inventory | Security scan |
|---|---|---|---|---|
| npmdodopayments-mcp | 2.49.0Current | Sep 5, 2026 | 2 toolsSucceeded · 0 resources · 0 prompts | Verified clean |
Enterprise protection
Continuously monitor this MCP for security risk
Independently scan the exact version your agents use, receive alerts when its risk changes, and investigate every finding with retained version evidence.
- Independent exact-version security scans
- Continuous release and vulnerability monitoring
- Risk-change alerts with capability context
- Historical evidence and API exports
Custom pricingContact salesTailored to your organization, integrations, data needs, and support requirements.
Current version evidence
| Provenance | artifact_hash_verified | Signature | — |
|---|---|---|---|
| MCP SDK | — | Artifact SHA-256 | 02ab2dc8b5244417ccb5ea98aa5190fc84c5fc846917e0881ac1c9a778a45813 |
| Scanner | mcp-proof-engine 0.1.0 | Scan completed | Sep 1, 2026 |
| Security rating | — | Methodology | — |
0Proven
215Clean
0Inconclusive
0Flaky
0Errors
Current protocol inventory
2025-06-18Negotiated protocol
dodopayments_apiServer-reported name
2Capability groups
Sep 1, 2026Observed
Tools 2
| Tool | Category | Annotations | Risk |
|---|---|---|---|
executeRuns 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 {}.Input schema{
"type": "object",
"properties": {
"code": {
"type": "string",
"description": "Code to execute."
},
"intent": {
"type": "string",
"description": "Task you are trying to perform. Used for improving the service."
}
},
"required": [
"code"
]
} | — | — | |
search_docsSearch 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.Input schema{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "The query to search for."
},
"language": {
"type": "string",
"description": "The language for the SDK to search for.",
"enum": [
"http",
"python",
"go",
"typescript",
"javascript",
"terraform",
"ruby",
"java",
"kotlin"
]
},
"detail": {
"type": "string",
"description": "The amount of detail to return.",
"enum": [
"default",
"verbose"
]
}
},
"required": [
"query",
"language"
]
}Annotations{
"readOnlyHint": true
} | — | Read only | — |
Resources 0
- None observed.
Resource templates 0
- None observed.
Prompts 0
- None observed.
Remote endpoints
| Endpoint | Transport | Authentication | Health | Observed |
|---|---|---|---|---|
| No verified remote endpoint is linked. | ||||
Dodo Payments MCP Server questions
How do I install Dodo Payments MCP Server?
Install the selected package version with: npm install --save-exact dodopayments-mcp@2.49.0
What tools does Dodo Payments MCP Server provide?
Dodo Payments MCP Server exposed 2 tools during independent protocol observation, including execute, search_docs.
Is Dodo Payments MCP Server secure?
Our scanner tested version 2.49.0 without proving a finding in the methods exercised. This is not a guarantee that every deployment is secure.
Explore related MCP server guides
Curated product and capability guides containing this catalog record.
Related MCP servers from this publisher
Related records share independently retained publisher or namespace evidence. They are not automatically endorsed alternatives.
- Dodo Payments Agent PluginAlso published under dodopayments · npm:@dodopayments/opencode-plugin · verified official distribution
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.