Claude Mastercard Developers connectorWhat Claude can do in your Mastercard Developers account.
The Claude Mastercard Developers connector exposes 9 tools, all 9 of them read tools. 0 write, 0 undocumented. Claude browses Mastercard's service catalogue, docs, API specs and authentication guides. Below: what you get out of each.
Verified Trustpilot reviews · AI, automation & growth agency
A Mastercard integration without digging through the portal
Plugging in a Mastercard API starts with reading: which service, which operations, how to authenticate. With this connector, Claude pulls those answers from the official documentation when you ask, instead of leaning on training data that may be out of date.
Pick the right service. get-services-list lists products and technical services with their title, description and ID.
Understand an API (the interface one program uses to talk to another) before writing code. get-api-operation-list summarizes every operation in a spec, then get-api-operation-details walks through parameters and request and response schemas for the one you care about.
Get past authentication. The OAuth (the protocol that handles permissions between apps) 1.0a, OAuth 2.0 and Open Finance guides come with code samples and best practices, in the programming language you ask for.
What the connector won't do: no source describes a call to a payment API or access to a Mastercard account. By default its sheet only exposes documentation reading. Nothing runs on its own either, so Claude looks things up when you ask. For unattended chains of steps, the tools on the Integrations hub do a different job.
Words to know before connecting Mastercard Developers
Five terms, explained once.
- Connector
- The bridge you set up once between Claude and a service you already use, so Claude can work with it while answering you.
- Tool
- A named capability the connector opens to Claude. Claude picks what it needs on its own; the directory sheet lists every one.
- Authorization
- The service's own screen where you hand Claude the access it will use. Granted once per person, and revocable.
- Approval
- The confirmation Claude waits for before an action that changes something in an account, shown in the chat at the right moment.
- MCP
- The open standard connectors are built on: it lets an assistant like Claude hold a conversation with an outside service.
Connect the Claude Mastercard Developers connector
- 01
Find Mastercard Developers in Claude
In Claude, open Customize, then Connectors, and spot Mastercard Developers. On a Team or Enterprise workspace, an Owner or Primary Owner enables it for the organization first; each member then connects on their own.
- 02
Start the connection
Click Connect on the Mastercard Developers row, then follow the window the service opens. If the link ever breaks, hit Disconnect and connect again from the same row.
- 03
Read the authorization screen
Go through the authorization screen before you accept. It belongs to the service, not to Claude, and it sets what the access covers. You can also take that access back later from the service itself.
Mastercard's 9 documentation tools
Mastercard Developers gives Claude 9 tools: 9 that read your account, 0 that change something in it.
Nine lookup tools, described by the tool list Mastercard's service publishes. Names stay in English, as Claude shows them.
- 9 read
What Claude reads (9)
9 toolsNine tools that read Mastercard Developers' public documentation.
get-services-list
Lists the products and services on the Mastercard Developers portal, with title, description and service ID. It's the entry point, since the other tools ask for that ID.
get-documentation
Shows the documentation outline for one service: section titles, descriptions and navigation links. You locate the service first with get-services-list.
get-documentation-section-content
Brings back a full documentation section, meaning a group of pages under one theme rather than a single page. For one page only, get-documentation-page does the job.
get-documentation-page
Retrieves one documentation page in full. Narrower than a section, for when you already know exactly what to read. For a whole group of pages, get-documentation-section-content is the one.
get-api-operation-list
Summarizes every operation in a Mastercard API spec: HTTP method, path, title and description for each. An overview before the details, which get-api-operation-details then provides.
get-api-operation-details
Unpacks a single operation: parameter definitions, request and response schemas, and the technical specs needed for a call to go through without errors. You pick the operation from the list get-api-operation-list returns.
get-oauth10a-integration-guide
Hands over Mastercard's OAuth 1.0a integration guide step by step, with code samples and best practices. You can name a language for tailored examples.
get-oauth20-integration-guide
Delivers the OAuth 2.0 counterpart: detailed instructions, sample code and recommendations, with the same option to pick a programming language. The guide covers Mastercard APIs.
get-openfinance-integration-guide
Returns the Open Finance integration guide, formerly Open Banking: setup steps, API usage examples and implementation best practices, in one document. Unlike the two OAuth guides, its description says nothing about picking a language.
What Claude asks first, and who can switch Mastercard Developers off
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. Here the nine tools read documentation, and no source describes an approval specific to any of them.
On Team and Enterprise, workspace owners decide whether a member may let certain actions through without being asked again. They can also limit what Mastercard Developers may do for the whole organization, keeping reading open and closing writes for example, with a setting nobody bypasses from their own account. Finally, Claude works with the connected person's rights: what that person can't reach, Claude can't reach either.
Which plans include it
None of the 819 directory sheets shows plan availability. Connector by connector, that information isn't published anywhere: it's a real gap in the catalogue.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens the connector for the organization first. For the current status on your account, the only reference is the Mastercard Developers sheet in the official directory, which the button on this page opens.
Where Mastercard Developers stops inside Claude
A connector isn't an automation: Claude calls these tools while answering you, and nothing runs in the background. Only Mastercard, the publisher, documents this connector.
The nine tools read the portal's public documentation; no source describes a call to a payment API or access to a Mastercard account. The sheet exposes reading only, which is an observed floor, not a guarantee. A connected community connector has exactly the same access as any other. The directory badge isn't a security audit, and Anthropic notes on every sheet that it doesn't control a publisher's tools. Other connectors are gathered on the Claude connectors page.
Need help connecting Mastercard Developers to Claude?
A person reads every message.