Skip to main content
plugin

mastercard-developers — GitHub Copilot plugin: install

This GitHub Copilot plugin supports integrations with Mastercard APIs. It adds API guidance and the Mastercard Developers MCP server.

MIT ★ 60 updated 2026-10-01

Install into GitHub Copilot · Command from the source All methods and platforms ↓
copilot plugin install mastercard-developers@awesome-copilot
Open on GitHub

What mastercard-developers does

The plugin helps build integrations with Mastercard APIs and apply Mastercard API guidance. Its package contains the mastercard-best-practices skill and MCP server configuration.

The package uses plugin.json and mcp.json, with streamable-http set as the transport for the remote MCP server. Both manifests require a $schema field. The copy of the skill in skills/ is generated from the main directory by node scripts/sync.js; edit the source copy instead.

What it helps with

  • build an integration with a Mastercard API
  • apply Mastercard guidance while working with an API
  • connect the Mastercard Developers MCP server

Example prompts for the agent

  • Help me build an integration with a Mastercard API.
  • Apply Mastercard Developers guidance to this code.
  • Connect the Mastercard Developers MCP server for API work.

How to install mastercard-developers

Command from the source

copilot plugin install mastercard-developers@awesome-copilot

Step by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own

Questions about mastercard-developers

How do I install mastercard-developers in GitHub Copilot?

Run copilot plugin install mastercard-developers@awesome-copilot.

What does mastercard-developers do?

It supports integrations with Mastercard APIs, with API guidance and the Mastercard Developers MCP server included.

Which transport does the mastercard-developers MCP server use?

Its configuration uses streamable-http for the remote MCP endpoint.

Source text

plugin · MIT
# Agent Plugin (portable)

This directory is a portable **[Agent Plugins v1](https://agent-plugins.org/specification)** package — a single, vendor-neutral layout that any conformant client (Claude Code, Codex, Cursor, Gemini CLI, Antigravity, …) can load without a provider-specific manifest.

```
plugin/
├── plugin.json   # Agent Plugins manifest ($schema + name + metadata)
├── mcp.json      # MCP server wiring (type: streamable-http)
└── skills/       # mastercard-best-practices (synced from /skills)
```

## Why this exists

The `providers/claude`, `providers/codex`, and `providers/cursor` folders each carry a near-identical copy of the same skill + MCP server wrapped in a different vendor manifest shape. Agent Plugins collapses that duplicated "box" into one portable directory:

| Concern | Vendor-specific plugins | Agent Plugin |
| --- | --- | --- |
| Manifest | `.claude-plugin/`, `.codex-plugin/`, `.cursor-plugin/` | single root `plugin.json` |
| MCP config | `.mcp.json` / `mcp.json`, `type: "http"` | `mcp.json`, `type: "streamable-http"` |
| Client-only fields | top-level (e.g. Codex `interface`) | `extensions.<reverse.domain>` (sanctioned home; see note) |

> **Client-only metadata is intentionally not duplicated here yet.** The Codex `interface` block (catalog display name, category, brand color, etc.) still lives in [`providers/codex/`](../../codex/). The Agent Plugins schema is closed, so any such client-specific data would have to move under `extensions."<reverse.domain>"` — but the exact namespace a client reads is client-defined and unverified for us, so we keep the portable manifest lean and vendor-neutral until a client confirms both native `plugin.json` loading and its extension namespace.

## Notable spec differences from the vendor copies

- **MCP transport type** is `"streamable-http"` (the Agent Plugins value for a remote MCP endpoint), not the vendor-native `"http"`.
- **`$schema` is required** on both `plugin.json` and `mcp.json`.
- **Client-specific data** (e.g. the Codex `interface` block) is **not** duplicated here — it stays in [`providers/codex/`](../../codex/). If a client ever needs it in the portable manifest, it must go under `extensions."<reverse.domain>"`, because the manifest schema is closed and rejects unknown top-level fields.

## Skills

The `skills/` copy is generated from the canonical [`/skills`](../../../skills) directory by `node scripts/sync.js`. Do not edit it directly.

© Mastercard · MIT · Mastercard/developers-agent-toolkit

Similar plugins

All plugins for Backend and APIs →

From the same set2

Project sponsors

Companies that keep this analytics open