OpenApps

Mastercard Developers MCP server — tools & history

Mastercard Developers MCP server: observed open status, tool schemas, linked apps and version history.

Mastercard Developers

Endpoint: https://developer.mcp.mastercard.com/

Observed status: open. Checked: 2026-10-11T06:23:43+00:00.

Linked apps

Observed tools

  • get-api-operation-details — Provides 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})
  • get-api-operation-list — Provides 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-documentation — Provides 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-page — Retrieves 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-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-oauth10a-integration-guide — Retrieves 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-guide — Retrieves 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-guide — Retrieves the comprehensive Open Finance (previously known as Open Banking) integration guide including setup instructions, API usage examples, and implementation best practices.
  • get-services-list — Lists 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.

Data as of 2026-10-11T06:23:43+00:00.

OpenApps records store listings and observed changes. Store ranks are not download counts; launch dates may be derived or use the first observation. Coverage gaps are shown in the interactive catalog.

REST API specification · Guide for AI clients · Manage API keys and MCP connections