A side-by-side look at the Mastercard Developers MCP and Vibie MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mastercard Developers MCP for developer tools work as a local process; choose Vibie MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
get-services-list, get-documentation, get-documentation-section-content.VIBIE_API_BASE.vibie_create_site, vibie_update_site, vibie_list_sites.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 67/100 · Great | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | OAuth 2.0 |
| Pricing | Free | Free |
| Required env vars | None listed | VIBIE_API_BASE |
| Verified owner | Community listing | Community listing |
| GitHub stars | 55 | 1 |
| Directory activity | 2 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 9 | 4 |
| Full listing | View Mastercard Developers MCP | View Vibie MCP |
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-content
Retrieves 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})vibie_create_siteCreate a NEW Vibie site by uploading a local folder. Use this when the user wants to publish a brand new site, or when no .vibie/site.json marker exists in the folder. Vibie hosts static HTML/CSS/JS at a permanent URL like my-site-a3f9.vibie.page. Auto-creates a .vibie/site.json marker in the folder for future updates.vibie_update_siteUpdate an existing Vibie site with new content from a local folder. Use this when the user wants to re-deploy or push changes to an already-published site. If .vibie/site.json marker exists in the folder, the slug is read automatically; otherwise pass slug explicitly. Same URL, new content.vibie_list_sitesList all sites owned by the current Vibie user. Returns slug, display name, category, URL, visibility, and last update time. Use this to discover what sites the user already has, e.g. before update.vibie_get_siteGet metadata for a single Vibie site by slug. Returns name, category, URL, visibility, like count, timestamps.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.
{
"mcpServers": {
"mastercard-developers-mcp": {
"command": "npx",
"args": [
"-y",
"@mastercard/developers-mcp"
]
}
}
}
{
"mcpServers": {
"shdomi8599-vibie-mcp": {
"command": "npx",
"args": [
"-y",
"vibie-mcp"
],
"env": {
"VIBIE_API_BASE": "YOUR_VIBIE_API_BASE_HERE"
}
}
}
}