Mastercard Developers MCP

io.github.MastercardPublished by GitHub account Mastercardv0.1.0Updated Oct 24, 2026

Access Mastercard Developers APIs, documentation, and API specifications through MCP.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

A local MCP server that gives an assistant read access to Mastercard Developers services, documentation, API specifications and OAuth integration guides.

What you can do
List Mastercard Developers products and services with titles, descriptions and service IDs, optionally narrowed to one service or API specification at startup. Browse a service's documentation overview, section titles and navigation links. Read the full content of a documentation section or page. Summarize an API specification's operations with HTTP methods, paths, titles and descriptions. Fetch parameter definitions and request/response schemas for a single API operation. Retrieve OAuth 1.0a, OAuth 2.0 and Open Finance integration guides with steps, code examples and best practices.
When to use it
Useful when building or debugging an integration against Mastercard APIs and you want the assistant to look up official documentation, operation schemas and authentication guidance without leaving the chat. Pre-configuring a service or specification URL keeps answers focused on one product.
Requirements
Runs locally over stdio via npx from the npm package @mastercard/developers-mcp; Node.js 18 or later. Network access to Mastercard Developers documentation and specification URLs. No accounts, API keys or environment variables are declared. Optional --service or --api-specification arguments focus the server; the specification argument overrides the service one and disables the services list tool.
Before you install
Documentation and specification content is fetched from Mastercard's public developer site, so the URLs given in configuration and the pages returned are third-party data. The server is read-only for documentation; it does not call Mastercard APIs or handle credentials itself. Review any code examples it returns before using them in a real integration.

Installation

In SourceWeft

  1. Open Mastercard Developers MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Mastercard Developers MCP Server

[mastercard developers logo]

A Model Context Protocol (MCP) server that provides access to Mastercard Developers documentation.

Overview

This MCP server acts as a bridge between MCP clients and Mastercard Developers resources, offering tools to:

  • List available Mastercard services
  • Query API specifications and their operations
  • Access documentation for each service
  • Retrieve integration guides for OAuth 1.0a, OAuth 2.0, and Open Finance

Available Tools

Service Discovery

  • get-services-list: Lists all available Mastercard Developers Products and Services with their basic information including title, description, and service ID.

Documentation

  • get-documentation: Provides an overview of all available documentation for a specific Mastercard service including section titles, descriptions, and navigation links.

  • get-documentation-section-content: Retrieves the complete content for a specific documentation section.

  • get-documentation-page: Retrieves the complete content of a specific documentation page.

API Operations

  • 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.

  • 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.

Integration Guides

  • 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.

  • 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.

  • get-openfinance-integration-guide: Retrieves the comprehensive Open Finance integration guide including setup instructions, API usage examples, and implementation best practices.

Configuration Options

You can pre-configure the server with a specific service or API specification by passing them as arguments. This is useful when you are working with a specific service, and you want to focus your agents

  • service: URL of the documentation of a service that you want the MCP to focus on e.g. https://developer.mastercard.com/mdes-customer-service/documentation
  • api-specification: URL of the API specification that you want the MCP tools to focus on e.g. https://static.developer.mastercard.com/content/match/swagger/match-pro.yaml. You can get the link from Download Spec button in the API Reference page of service. NOTE: Specifying this will override any value provided in service configuration.

If you specify service or api-specification then the get-services-list tool will be disabled.

Integration with MCP Clients

To use this server with MCP clients like Claude Desktop, add it to your MCP configuration:

json
{  "mcpServers": {    "mastercard-developers": {      "command": "npx",      "args": ["-y", "@mastercard/developers-mcp"]    }  }}

For Specific Service

json
{  "mcpServers": {    "mastercard-developers": {      "command": "npx",      "args": [        "-y",        "@mastercard/developers-mcp",        "--service=https://developer.mastercard.com/open-finance-us/documentation/"      ]    }  }}

For Specific API Specification

json
{  "mcpServers": {    "mastercard-developers": {      "command": "npx",      "args": [        "-y",        "@mastercard/developers-mcp",        "--api-specification=https://developer.mastercard.com/open-finance-us/swagger/openbanking-us.yaml"      ]    }  }}

Usage with VSCode

For quick installation, use one of the one-click installation buttons below:

[Install with NPX in VS Code] [Install with NPX in VS Code Insiders]

For manual installation, add the following JSON block to your User Settings (JSON) file in VS Code. You can do this by pressing Ctrl + Shift + P and typing Preferences: Open Settings (JSON).

Optionally, you can add it to a file called .vscode/mcp.json in your workspace. This will allow you to share the configuration with others.

Note that the mcp key is not needed in the .vscode/mcp.json file.

NPX

json
{  "mcp": {    "servers": {      "mastercard-developers": {        "command": "npx",        "args": ["-y", "@mastercard/developers-mcp"]      }    }  }}

You can also provide configuration options as arguments, see above for examples.

Development

Pre-requisites: Node.js 18+

  1. Install dependencies:

    bash
    npm install
  2. Build the project:

    bash
    npm run build
  3. Run tests:

    bash
    npm run test
  4. Start the server:

    bash
     npm run start

Watch for changes during development:

bash
npm run watch

The server runs on stdio and will be available for MCP client connections.

With Configuration Options
bash
# Pre-configure with a documentation URLnpm run start -- --service=https://developer.mastercard.com/open-finance-us/documentation/
# Pre-configure with an API specification pathnpm run start -- --api-specification=https://static.developer.mastercard.com/content/open-finance-us/swagger/openbanking-us.yaml

To build the DXT file

You can build the DXT file for one-click installation for Claude Desktop by running:

bash
npm run build-dxt

Debugging the server

bash
npx @modelcontextprotocol/inspector node dist/index.js

References

Source: modelcontextprotocol/README.md at commit 24df3ad

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts