3 connectors, live from D1
Connectors
MCP concepts, known pre-built connectors, and this repo's own dogfooded naming pattern, grouped by category unless filtered.
| connector | real/pattern | description |
|---|---|---|
| cloud__docker_mcp__engineering_coworker | real | Real example instance of the naming ontology: Claude inference running in Anthropic's cloud, connecting to MCP servers via the Docker Desktop MCP Toolkit catalog (17 servers snapshotted at time of writing), still acting as the engineering coworker persona. The point of naming both surfaces explicitly is that code written for cloud__* must only use mcp__MCP_DOCKER__* tools, while code for macos__* can use npx/binary MCPs directly on the Mac. |
| macos__desktop_cowork__engineering_coworker | real | Real example instance of the naming ontology: Claude Desktop Cowork running on macOS, acting as the engineering coworker persona — corresponds to profiles/claude_desktop_cowork.json and the Docker MCP profile of the same name, which wires in Cloudflare + GitHub + filesystem + chrome-devtools (npx) + the engineering-coworker Rust binary as MCP servers. |
| This repo's naming ontology: {device_surface}__{client_surface}__{coworker_enum} | pattern | This repo names its own MCP-connected surfaces with a fixed three-part convention — device_surface (where the model or Claude client runs), client_surface (which Claude product/UI is in use), and coworker_enum (which coworker persona this surface acts as) — so that code written for one surface cannot silently assume tools only available on another. |
Machine-readable version: GET /api/connectors?category=repo_pattern