Source: wiki synthesis: nate-herk-every-level-of-claude, essential-mcp-servers, ben-every-cowork-feature-explained
Connectors are the Anthropic-maintained, OAuth-managed set of MCP server integrations bundled directly into Claude.ai and Cowork. As of mid-2026 the catalog spans 50+ services across communications, docs, engineering, CRM, design, and project management — Slack, Google Drive, Gmail, GitHub, Notion, Google Calendar, Asana, Atlassian, Box, Canva, ClickUp, Fathom, Figma, HubSpot, Intercom, Linear, monday.com, and more. The defining shift: connectors replace the paste-to-prompt workflow (“let me copy this thread / spec / ticket into chat”) with direct, authenticated API access that Claude can call as a tool.
Key Takeaways
- 50+ connectors as of 2026-05 — Slack / Google Drive / Gmail / GitHub / Notion / Calendar named explicitly in the Nate Herk Level 2 surface walkthrough; the broader catalog covers comms, docs, engineering, CRM, design, and PM SaaS.
- OAuth-managed. One-click connection — the user authorizes the service, Anthropic handles token storage and refresh. No
.mcp.json, no credential JSON, no MCP-server-URL paste step. ^[inferred] - Replaces paste-to-prompt. Instead of “let me paste the thread” the user says “summarize threads from marketing last week” or “pull the latest spec doc” and Claude calls the connector directly (Nate Herk L2).
- Same catalog in Claude.ai and Cowork. Connectors set up in claude.ai chat are available in Cowork; the Cowork-side surface adds plugins that bundle connectors + skills + sub-agents. ^[inferred]
- What connectors cover vs what requires Computer Use. If a SaaS tool is in the connector catalog (or has a community MCP), use the connector. For apps without a connector AND without an MCP, fall back to Computer Use / browser use — both Ben and Nate Herk flag this as “last resort, high-token-cost, error-prone.”
- Free vs paid split. Connectors are available on free Claude.ai (subject to per-connector limits) ^[inferred]; the same connectors work in paid-tier Cowork without paywall.
- The fallback ladder when a connector doesn’t exist: (1) check the connector catalog → (2) Google
<software> + MCPfor a community MCP → (3) build your own MCP via Anthropic’s built-in MCP builder skill → (4) Computer Use as last resort (Ben’s three-step ladder). - Observability dashboard for connector developers (2026-06-09). [X signal — @ClaudeDevs 2026-06-09] Anthropic shipped an observability dashboard for developers building connectors — visibility into how third-party tools and data brought to Claude via MCP are actually used. First-party tooling for the connector-builder side (distinct from the one-click end-user install surface above). (Source:
raw/x-bookmarks-recent-digest-2026-06-09.md, https://x.com/ClaudeDevs/status/2064072801062121906.) - Enterprise-Managed Auth for MCP (beta, 2026-06-18). [X signal — @ClaudeDevs] Centralized, IdP-based authorization (e.g., Okta) for connectors: admins manage access to tools and data sources once, and users get seamless connections on first login across Claude chat, Claude Code, and Cowork. Beta connectors include Asana, Atlassian, Canva, Figma, Linear, Slack, Supabase. This extends the one-click per-user OAuth model above to org-managed identity — the enterprise evolution of the connector-auth story. (Source:
raw/x-account-claudedevs-2067655887662272723.md, https://x.com/ClaudeDevs/status/2067655887662272723.)
Connector vs MCP server (the distinction)
Connectors and MCP servers are not different things — they speak the same protocol. The distinction is who maintains, hosts, and authenticates them:
| Dimension | Connectors | ”Raw” MCP servers |
|---|---|---|
| Maintained by | Anthropic (curated, vendor-blessed) | Anyone — vendor, community, or self |
| Auth | OAuth, managed by Anthropic | User-supplied tokens / API keys / OAuth flows |
| Install | One click in claude.ai / Cowork settings | .mcp.json paste, custom URL, or stdio config |
| Discovery | Built-in catalog | Google <software> + MCP, GitHub search, marketplaces |
| Coverage | 50+ named SaaS services | 800+ public servers, niche tools, internal systems |
| Audit burden | Anthropic vetted | User audits source code, permissions, scopes (essential-mcp-servers security section) |
Connectors are the curated, low-friction subset; raw MCP is the broader, higher-ceiling, higher-burden ecosystem. Both ultimately plug into Claude via the MCP protocol — only the packaging differs. ^[inferred]
Top connector use cases by category
| Category | Connectors | Common asks |
|---|---|---|
| Communications | Slack, Gmail | ”Summarize marketing this week” / “Draft a reply to the last email from X” |
| Docs + knowledge | Google Drive, Notion, Box | ”Pull the Q2 launch spec” / “Find the doc where we decided pricing” |
| Engineering | GitHub, Linear, Sentry, Atlassian (Jira + Confluence) | “Review PR #847” / “Triage Linear tickets tagged P1” / “Pull the stack trace for issue X” |
| CRM + support | HubSpot, Intercom | ”Last 10 conversations with Acme Corp” / “Update the deal stage” |
| Design | Figma, Canva | ”Pull the design from this Figma frame” / “Open the latest Canva draft” |
| Project management | Asana, ClickUp, monday.com | ”Today’s tasks across boards” / “Update sprint status” |
| Meetings | Google Calendar, Fathom | ”Prep for my 10am” / “Summarize yesterday’s meeting and extract action items” |
This list is the named-connector slice ^[inferred] — the full Anthropic catalog updates frequently as new partners ship integrations.
Related
- MCP — the underlying protocol
- Essential MCP Servers — the raw / community side of the same ecosystem
- Every Cowork Feature Explained (Ben) — Layer 3 places connectors in the broader plugin + MCP ladder
- Every Level of Claude (Nate Herk) — Level 2 names the 50+ figure and the canonical connector list
- Computer Use — the last-resort fallback when no connector or MCP exists
- Cowork Plugins — bundles of connectors + skills + sub-agents
- Claude Projects — connectors compose into project-level context
Try It
- Audit your current connector set. In claude.ai → settings → connectors (or Cowork → customize → connectors), list every connector you’ve connected. For each, ask: am I still pasting content from this app into chat? If yes, the connector is underused.
- Connect one high-frequency SaaS you’ve been pasting from. Most-impact first connects: Slack (comms volume), Google Drive or Notion (docs), Gmail (mail triage), GitHub (eng workflow), Google Calendar (meeting prep). One-click OAuth — no config files.
- Test the ladder when something’s missing. If a tool you need isn’t in the connector catalog, try the fallback ladder: search the MCP ecosystem for a community server, then consider the built-in MCP builder skill (Ben’s example: he built his own Circle.so + Reddit MCPs this way) before reaching for Computer Use.