MCP Clients Registry

A community-maintained map of MCP clientinfo.name values to official client names and metadata. Use it to identify clients behind unfamiliar names and improve reporting and insights.

Known clients

This registry contains 61 MCP clients.

Data format

All data lives in clients.json. The top-level object contains a single field:

• clients: Map of clientinfo.name -> metadata object

Example:

{
  "clients": {
    "cursor-vscode": {
      "official_name": "Cursor",
      "owner": "Anysphere",
      "url": "https://www.cursor.com",
      "description": "AI-powered coding IDE based on VS Code.",
      "tags": ["coding-agent", "ide", "vscode-fork"],
      "aliases": ["cursor", "Cursor"]
    }
  }
}

Client object fields

• official_name (string, required)
• owner (string, optional)
• url (string URL, optional)
• description (string, optional)
• aliases (array of strings, optional)
• tags (array of strings, optional)

The key under clients must equal the MCP clientinfo.name. If a client has other known names, list them in aliases.

Contributing

1. Add or update an entry in clients.json.
2. Keep entries in alphabetical order by key.
3. Prefer official sources for url.
4. Only add aliases that are known to appear in the wild.

Maintenance script

• Validate and sort: node clients.mjs
• Add a new entry interactively: node clients.mjs --add

npm package

const { getMCPClient, mcpClients } = require("mcp-client-registry");

const client = getMCPClient("cursor-vscode");
if (client) {
  console.log(client.official_name);
}

console.log(Object.keys(mcpClients).length);

getMCPClient(name) matches both canonical keys and known aliases.

Package source lives in packages/node. clients.json for the npm package is generated via packages/node/scripts/sync-clients.mjs.