14 connectors, live from D1
Connectors
MCP concepts, known pre-built connectors, and this repo's own dogfooded naming pattern, grouped by category unless filtered.
concept
| connector | real/pattern | description |
|---|
| Connectors vs. custom tools |
real |
A "connector" is typically a pre-built, ready-to-use integration (often maintained by Anthropic or a third party) that wraps an MCP server for a specific external product, so a user can enable it without writing any code. A "custom tool" is a tool an application or developer defines and registers directly (for example, in the Managed Agents API or via a hand-written MCP server) — it is not necessarily wrapped in a pre-built connector UI, and it can be scoped to exactly the actions an application wants to allow. |
| Connectors are one instance of a broader MCP-server ecosystem |
real |
Beyond the handful of well-known pre-built connectors, Claude can connect to any MCP server a user or organization stands up themselves — including this repo's own filesystem, Cloudflare, Postgres, and engineering-coworker MCP servers, none of which are "pre-built connectors" in the marketed sense but which use the identical MCP transport and tool-call mechanism. |
| Model Context Protocol (MCP) |
real |
MCP is an open protocol that lets an AI assistant like Claude connect to external data sources and tools through a standardized server interface, rather than each integration being bespoke. An MCP server exposes a set of tools (and sometimes resources/prompts) over a defined transport (e.g. stdio or HTTP), and any MCP-compatible client — Claude Desktop, Claude Code, Claude cloud products — can connect to it using the same protocol. |
prebuilt_connector
| connector | real/pattern | description |
|---|
| Asana connector |
real |
A commonly available connector for reading and updating Asana tasks/projects, letting Claude help triage, summarize, or create work items in a connected workspace. |
| Atlassian (Jira/Confluence) connector |
real |
A commonly available connector for reading and updating Jira issues and/or Confluence pages, letting Claude help with ticket triage, status reporting, or documentation lookups in a connected Atlassian workspace. |
| Docker Desktop MCP Toolkit |
real |
A catalog/management surface bundled with Docker Desktop for discovering and connecting MCP servers as containerized services — this repo snapshots 17 servers from that catalog for the cloud__docker_mcp__engineering_coworker surface. |
| Google Drive connector |
real |
A commonly available connector that lets Claude search and read files stored in a user's or workspace's Google Drive as part of a conversation, subject to the connecting account's own permissions. |
| GitHub connector / MCP server |
real |
A widely used connector/MCP server for reading and, where permitted, modifying GitHub repositories — issues, pull requests, code search, commits — used heavily in this repo's own Cowork/Code sessions. |
| Linear connector |
real |
A commonly available connector for reading and updating Linear issues, useful for engineering-workflow assistance (triage, status summaries, drafting issue descriptions). |
| Notion connector |
real |
A commonly available connector for reading and, where permitted, editing Notion pages/databases, useful for pulling in team documentation or knowledge-base content during a conversation. |
| Slack connector |
real |
A commonly available connector that lets Claude read and, where permitted, post to Slack channels/messages the connected account has access to — useful for summarizing threads or drafting replies. |
repo_pattern
| 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