INDIVIDUAL MCP TOOL

get_client

Everything documented about one client: config file paths (project/global/enterprise), formats, and the typed fields each surface accepts.

clients.devnone authenticationAvailability not checked

LIVE ENDPOINT

https://clients.dev/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_client and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.clients-dev]
url = "https://clients.dev/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "clients-dev": {
      "type": "http",
      "url": "https://clients.dev/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: clients-dev
Remote MCP URL: https://clients.dev/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "clients-dev": {
      "url": "https://clients.dev/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "clients-dev": {
      "type": "http",
      "url": "https://clients.dev/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "clients-dev",
  "transport": "streamable-http",
  "url": "https://clients.dev/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

list_clients — List every AI coding client in the clients.dev catalog with vendor, type, and which config surfaces are documented.
compare_surface — How every documented client handles one config surface (mcp, skills, rules, hooks, commands, settings) — file paths, formats, transports, and fields.
get_config_schema — JSON Schema for the fields a client accepts on one surface — use it to generate or validate config (e.g.