Dodo Agent Plugin vs Mastercard Developers MCP
A side-by-side look at the Dodo Agent Plugin and Mastercard Developers MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Dodo Agent Plugin for finance & fintech work as a local process; choose Mastercard Developers MCP for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Dodo Agent Plugin when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
execute, search_docs.
Choose Mastercard Developers MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
get-services-list, get-documentation, get-documentation-section-content.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 85/100 · Excellent | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 6 | 55 |
| Directory activity | 5 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 2 | 9 |
| Full listing | View Dodo Agent Plugin | View Mastercard Developers MCP |
Tools & capabilities
Dodo Agent Plugin tools 2
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 {}.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.
Mastercard Developers MCP tools 9
get-services-listLists all available Mastercard Developers Products and Services with their basic information including title, description, and service id. IMPORTANT: The response contains both 'Products' (business offerings) and 'Services' (technical APIs with serviceIds). Use "serviceId" for each service for any tools that require serviceId as the parameter.get-documentationProvides an overview of all available documentation for a specific Mastercard service including section titles, descriptions, and navigation links. It takes one argument: - serviceId (str): The unique identifier of the Mastercard service (e.g., 'send', 'loyalty', 'locations')get-documentation-section-contentRetrieves the complete content for a specific documentation section. IMPORTANT: A section is not a single page, but rather a collection of pages that are grouped together. It takes two arguments: - serviceId (str): The unique identifier of the Mastercard service (e.g., 'send', 'loyalty', 'locations') - sectionId (str): The specific section identifier within the service documentation (e.g., 'getting-started', 'api-reference')get-documentation-pageRetrieves the complete content of a specific documentation page. Takes one argument: - pagePath (str): The full path to the documentation page (e.g., '/send/documentation/use-cases/index.md')get-oauth10a-integration-guideRetrieves the comprehensive OAuth 1.0a integration guide including step-by-step instructions, code examples, and best practices for Mastercard APIs. Optionally specify a programming language to get language-specific examples and guidance.get-oauth20-integration-guideRetrieves the comprehensive OAuth 2.0 integration guide including step-by-step instructions, code examples, and best practices for Mastercard APIs. Optionally specify a programming language to get language-specific examples and guidance.get-openfinance-integration-guideRetrieves the comprehensive Open Finance (previously known as Open Banking) integration guide including setup instructions, API usage examples, and implementation best practices.get-api-operation-listProvides a summary of all API operations for a specific Mastercard API specification including HTTP methods, request paths, titles, and descriptions. It takes one argument: - apiSpecificationPath (str): The path to the API specification file e.g., '/open-finance-us/swagger/openbanking-us.yaml')get-api-operation-detailsProvides detailed information about a specific API operation including parameter definitions, request and response schemas, and technical specifications for successful API calls. It takes three arguments: - apiSpecificationPath (str): The path to the API specification file (e.g. The path would be /open-finance-us/swagger/openbanking-us.yaml for https://static.developer.mastercard.com/content/open-finance-us/swagger/openbanking-us.yaml, https://developer.mastercard.com/open-finance-us/swagger/openbanking-us.yaml, or /open-finance-us/swagger/openbanking-us.yaml) - method (str): The HTTP method of the operation (e.g., GET, POST, PUT, DELETE) - path (str): The API endpoint path from the specification (e.g., /payments, /accounts/{id})
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Dodo Agent Plugin
{
"mcpServers": {
"dodopayments-dodo-agent-plugin": {
"command": "npx",
"args": [
"-y",
"dodopayments-mcp@latest"
]
}
}
}
Mastercard Developers MCP
{
"mcpServers": {
"mastercard-developers-mcp": {
"command": "npx",
"args": [
"-y",
"@mastercard/developers-mcp"
]
}
}
}
Frequently asked questions
Dodo Agent Plugin is categorized under Finance & Fintech and uses a local stdio subprocess. Mastercard Developers MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick Dodo Agent Plugin for finance & fintech work and Mastercard Developers MCP for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Dodo Agent Plugin is listed as free. Auth: oauth 2.0. Mastercard Developers MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add dodopayments-dodo-agent-plugin and mastercard-developers-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dodo Agent Plugin has a quality signal of 85/100 (Excellent) with 5 views, 0 installs and 6 GitHub stars. Mastercard Developers MCP has 67/100 (Great) with 2 views, 0 installs and 55 GitHub stars.