Dodo Payments Agent Plugin
OfficialRelated Servers
Alternatives to Dodo Payments Agent Plugin
AlicenseNot gradedqualityBmaintenanceThe 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. It enables autonomous agents to securely act on behalf of users using the Dodo Payments1,194 npm54Apache 2.0
Related Servers
- AlicenseNot gradedqualityAmaintenanceUnofficial MCP server for the Apps API that enables managing customers, payments, plans, coupons, and Discord integration through natural language.24 npm2MIT

OrcaRail MCPofficial
AlicenseBqualityAmaintenanceOfficial MCP server for accepting crypto payments through OrcaRail. It enables AI agents to create payment intents, manage subscriptions, handle product catalogs, and get exchange rates via natural language.252 npmMIT- AlicenseNot gradedqualityBmaintenanceMCP server for the YooKassa payment API, enabling AI assistants to manage payments, refunds, receipts, webhooks, and saved payment methods through natural language.MIT

@gravv/mcpofficial
AlicenseAqualityAmaintenanceMCP server for the Gravv payments API that lets AI assistants onboard customers, run KYC, open accounts, move money, issue cards, and exchange currency, with built-in documentation search and safety confirmations for money-moving operations.23 npmMIT- AlicenseBqualityDmaintenanceMercado Pago's Official MCP Server offers tools so that developers can easily interact with our API using natural language, which simplifies tasks and product integration. Remotely hosted by Mercadolibre supporting Streamable HTTP Transport. Details on how to connect: https://mcp.mercadopago.com/18Apache 2.0
- AlicenseNot gradedqualityCmaintenance37 MCP servers for agentic commerce and Brazilian services. Covers Stripe ACP, x402 (Coinbase), AP2 (Google), Google UCP, plus 14 traditional Brazilian payment rails, fiscal, banking, communication, logistics, ERP, identity, and crypto APIs. ~480 tools. Supports stdio and Streamable HTTP.271MIT
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: execute runs JavaScript to interact with the API, while search_docs retrieves documentation. There is no ambiguity between them.
Both tool names use a verb-based pattern: 'execute' and 'search_docs'. This is consistent and clear, following a simple imperative style.
With only 2 tools, the set is minimal but well-scoped for its design: a single execute tool covers all API operations via code, and search_docs provides necessary documentation. This unconventional approach earns a slightly reduced score but is still reasonable.
The execute tool can perform any CRUD operation on the Dodo Payments API through TypeScript code, providing full coverage of the domain. The search_docs tool ensures agents can discover the correct methods. No obvious gaps exist.