Source: wiki synthesis: nate-herk-every-level-of-claude, essential-mcp-servers, ben-every-cowork-feature-explained. Added 2026-10-28: raw/How_to_Connect_ANY_App_to_Claude_Instantly_with_1_click.md (Ben AI, see § Ben AI field notes).

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.
  • 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.
  • 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> + MCP for 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.)
  • Salesforce in Claude (official promo, 2026-09-15). Anthropic posted a 1:24 video, “Salesforce in Claude” (youtube.com/watch?v=t6z0Ea0GwSk, raw/Salesforce_in_Claude.md). Its transcript is music only, so it gives no setup or tool detail. Elsewhere Anthropic names Salesforce as a data source for Claude Dashboards and as a connector usable from the Google Workspace add-on. This wiki has no first-party Salesforce connector page yet.

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:

DimensionConnectors”Raw” MCP servers
Maintained byAnthropic (curated, vendor-blessed)Anyone — vendor, community, or self
AuthOAuth, managed by AnthropicUser-supplied tokens / API keys / OAuth flows
InstallOne click in claude.ai / Cowork settings.mcp.json paste, custom URL, or stdio config
DiscoveryBuilt-in catalogGoogle <software> + MCP, GitHub search, marketplaces
Coverage50+ named SaaS services800+ public servers, niche tools, internal systems
Audit burdenAnthropic vettedUser audits source code, permissions, scopes ([[claude-ai/essential-mcp-servers

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.

Top connector use cases by category

CategoryConnectorsCommon asks
CommunicationsSlack, Gmail”Summarize marketing this week” / “Draft a reply to the last email from X”
Docs + knowledgeGoogle Drive, Notion, Box”Pull the Q2 launch spec” / “Find the doc where we decided pricing”
EngineeringGitHub, Linear, Sentry, Atlassian (Jira + Confluence)“Review PR #847” / “Triage Linear tickets tagged P1” / “Pull the stack trace for issue X”
CRM + supportHubSpot, Intercom”Last 10 conversations with Acme Corp” / “Update the deal stage”
DesignFigma, Canva”Pull the design from this Figma frame” / “Open the latest Canva draft”
Project managementAsana, ClickUp, monday.com”Today’s tasks across boards” / “Update sprint status”
MeetingsGoogle 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.

Eliot Prince field notes (2026-07 to 2026-10): custom connectors and a marketing stack

Source: raw/5_Claude_MARKETING_Connectors_I_Can_t_Live_Without.md (Eliot Prince, YouTube, 18:15, published 2026-08-26, https://www.youtube.com/watch?v=4wN_xg0bcyY); raw/How_to_Connect_Claude_to_Google_Search_Console_and_Analytics.md (6:51, 2026-08-15, https://www.youtube.com/watch?v=9J_m6uUSFBI); raw/Claude_Just_Changed_SEO_AI_Search_Forever.md (43:32, 2026-10-22, https://www.youtube.com/watch?v=setxOzrPVkU); raw/This_Claude_+_Apify_Workflow_Delivered_160_New_Leads_in_10_mins.md (23:41, 2026-07-07, https://www.youtube.com/watch?v=aWkMt7-4X38).

Four creator videos fill in the custom-connector side of the table above: the step where you paste a server URL, which the Key Takeaways said native connectors don’t need.

  • Custom connector flow (claude.ai / Desktop). Customize → Connectors → Add → Add custom connector → paste the vendor’s remote MCP server URL → give it a name → ignore Advanced settings → Add → Connect (OAuth login to the vendor). Eliot: “If anyone ever gives you a string like this and says, ‘this is a custom MCP’, this is where you put it.” After connecting, the connector page lists every tool, and each one can be set to always allow, needs approval, or blocked.
  • Middleware is a fourth rung on the fallback ladder. Composio is one custom connector that fronts thousands of apps. Eliot uses it for Google Search Console and Google Analytics, which “don’t exist” as native connectors as of his August and October 2026 videos. It also handles multiple Gmail or Outlook accounts, LinkedIn, Twitter and Reddit. Setup: at dashboard.composio.dev, use the For You view, not “Platform”; connect each app there with that app’s own OAuth; then add Composio to Claude as a custom connector. In prompts, name the route: “go into my Composio connector and check the key Search Console stats for .” This sits alongside the Zapier MCP bridge noted in Claude for Small Business. ^[inferred]
  • Connector discovery setting. Settings → Capabilities has a “connector search” toggle: “Let Claude search for connected directory and surface ones relevant to your conversation.” Eliot’s way to find connectors: ask Claude to review his last two weeks of work and suggest connectors that would remove copy-paste steps. That is how he found DataForSEO.
  • His five marketing connectors (August 2026):
ConnectorTypeWhat he uses it forCost as he states it
DataForSEOCustom (URL from dataforseo.com)Keyword volume, competition and CPC; YouTube organic search; backlinks; LLM and AI mentions; Amazon keywords. Used to write keyword-rich YouTube descriptionsAbout 50 top-up “nearly 3 years” at his usage
ApifyNative directory; Desktop; needs Apify API tokenScraping Google Maps, Meta Ad Library, LinkedIn jobs, social profiles (63,932 actors, he says)$5 free usage per month
Hyperframes by HeyGenNative directoryMotion-graphic overlays and explainer clips from chat. He calls it “experimental”Not stated
Kit (ConvertKit)Custom: app.kit.com/mcpReads sequences and subscriber health, and creates sequences (write access)Not stated
ComposioCustom (URL from Composio dashboard)GSC, GA, multiple Gmail accounts, LinkedIn, Reddit”absolutely free to use”
  • Connectors plus a live artifact give you a dashboard with no uploads. Eliot’s main reason for wiring data connectors is so live artifacts can pull and refresh data themselves “rather than you uploading spreadsheets”. Examples: a Kit list-health artifact with “top three actions each week”, and a YouTube morning dashboard.

  • Lead-gen additions (July 2026). Vibe Prospecting (vibeprospecting.ai, listed in the Claude directory, 400 starter credits) enriches scraped lists with decision-maker names and verified emails. The Gmail connector drafts but, in his default setup, does not send. Sending, and multiple Gmail accounts, need “extra in-depth” connector setup, which he did not show. See Cowork + Apify.

  • Turn publishing connectors off while you review. In the October SEO video he disconnects his Replit connector before the execution step because it “has a habit of auto publishing stuff”, and reconnects it once he has approved the output.

  • Separate Google Docs connector (October 2026). In chat mode Claude now offers a dedicated Google Docs connector, where before there was only Google Drive. With it connected, Claude edited the linked Google Doc directly. The same video covers the Docs, Sheets and Slides sidebar add-on, which brings your skills and connectors along: see Claude in Office and Google Workspace; Anthropic documents these as the Google Workspace connectors (beta) in Claude for Google Workspace. (Source: raw/Claude_for_Google_Workspace_just_dropped_and…md, 2026-10-06.)

Full workflows built on this stack: Claude SEO and AI Search Project and Claude as an Autonomous WordPress SEO Manager.

Futurepedia field notes (April to August 2026)

Source: raw/Use_Claude_Better_Than_99%of_People_Beginner_to_Pro.md (2026-08-16), raw/The_3_Most_Powerful_Claude_Features_Beginners_Don_t_Know_About.md (2026-05-13), raw/Full_Claude_Tutorial-_Beginner_to_Advanced_in_19_Minutes.md (2026-04-08), Futurepedia, YouTube. Series summary in The Claude Ecosystem in Four Layers (Futurepedia).

  • Add an image generator through a custom connector. Claude has no image generator of its own, so Futurepedia connects Higgsfield as a custom connector (Add → Add custom connector → name plus the URL the vendor lists → log in) and then asks Claude for images or videos directly. He names Magnific and Runway as other options.
  • Connectors as fast context. Gmail shows Claude how you reply and which clients and projects are active; Calendar keeps it current on your schedule; Granola brings meeting notes; Google Drive gives it your files.
  • Depth varies by tool. Some connectors are read-only and some can act; the connect screen lists each capability so you choose what to allow. His examples of actions: create and assign Asana tasks, and “pull my last Granola meeting and draft a follow-up email in Gmail” without switching tabs.

Brock Mesarich field notes (September 2026): Zapier MCP for apps with no native connector

Source: raw/Anthropic_Just_Dropped_Claude_2.0_Full_Breakdown.md (Brock Mesarich, YouTube @BrockMesarich, https://www.youtube.com/watch?v=lrsW8k-dHSk, uploaded 2026-09-17). What the Zapier MCP is, its app catalog and its per-call task billing are covered in Zapier; this section records only his setup and example.

  • The gap. Brock Mesarich runs his email marketing in Drip. Searching the Claude connector directory for Drip returns nothing, so he routes it through the Zapier MCP, which he says connects to “9,000 plus” apps.
  • Setup as he shows it:
    1. Create a Zapier account.
    2. In Zapier MCP, click Add MCP server (he already had one set up for Claude).
    3. Add the apps you want. He searched for Drip, selected all of its tools (“all the actions that this can perform for us”), then clicked Add tool.
    4. Open Connect on the server, copy the prompt shown there, and paste it into Claude.
    5. When Claude asks for permission, click Always allow. Claude then reported his Zapier server connected to 40 apps.
  • More apps, same server. Each new app is added to the same Zapier server; his advice is to “add as many apps as you would like”.
  • The Drip example. In a new Cowork chat he chose Output → Docs and asked Claude to “use the Zapier MCP in order to go and analyze my Drip campaigns” and break down the statistics that matter. A couple of minutes later it returned an editable Doc with subscriber and unsubscribe counts, every campaign he had run, and what was and was not working. The Docs output is described in Claude Dashboards and Motion.
  • Name the route in the prompt. His prompt names the Zapier MCP explicitly, the same habit Eliot Prince uses with Composio above.

Ben AI field notes (August 2026): Composio as the one connector for a team

Source: raw/How_to_Connect_ANY_App_to_Claude_Instantly_with_1_click.md (Ben AI, YouTube, https://www.youtube.com/watch?v=M_E460gRHIQ, 9:50, uploaded 2026-08-24). Ben says the video is not sponsored and that his agency now connects all its software to Claude through Composio. The captions spell it “Compozio” in places. His paid-community pitch is left out.

Eliot Prince’s notes above cover Composio for a solo marketer. Ben’s adds the reasons an agency or team would standardise on it.

  • One connector, 1,000+ apps. Most apps connect with a login rather than an API key. Ben names every Google product (Sheets, Drive, Docs, Analytics, Slides), Microsoft products, Meta Ads, Google Ads, LinkedIn Ads, Instagram, LinkedIn, WhatsApp, X and YouTube. In a prompt, Composio routes each step to the right app; his example read a Notion outline, ran his intro-writer skill and wrote the result to a Google Doc.
  • Deeper tool sets. Ben counts 27 tools in Claude’s built-in Gmail connector, with no send action, against 63 in Composio’s Gmail toolkit, which can send. The no-send point agrees with Eliot’s “drafts but does not send” above; the counts are Ben’s and were not checked.
  • Several accounts of one app. He connects his work and personal Gmail and asks Claude to “analyze both my email inboxes and flag anything that came in over the last 24 hours.” The same works for teammates’ accounts.
  • Set up once, use in any AI tool. The same Composio connections work in Codex, Grok or any client that takes the connector, so you don’t redo auth per tool.
  • Team rollout without sharing passwords. The admin logs in to each app inside Composio and shares the Composio connector; teammates never see the credentials. Teammates can also join the account and log in to their own apps. Per-app scopes decide which actions are allowed, and everyone on the connection inherits them. He mentions a “Composio for teams” tier with more controls but had not tried it.
  • No upkeep. Composio handles reconnections and keeps the toolkits updated, where native connectors need re-linking “every couple of weeks” in his experience and custom MCPs need maintaining.
  • Fewer tokens at chat start. Every connector or MCP you install loads its tool definitions into each new chat; he shows about 10,000 tokens of MCP tools in a fresh Claude Desktop chat with most connectors already off, and points to /context in the Claude Code tab to see yours. One Composio connector replaces 30 to 50 separate ones. In Claude Code, Tool Search already defers MCP tool schemas until needed (MCP), so the saving there is likely smaller than in Desktop.
  • Limitation he admits. Some Composio toolkits “are not working perfectly yet.”
  • Setup. Make a Composio account → Connect apps → connect each one → Connect to my agent → pick the platform for instructions. In Claude Desktop he finds Composio under Browse connectors and connects it from there. Eliot, two days later, added it as a custom connector by URL. Either route ends in the same connector.
  • Pricing, as Ben states it and as checked. Ben: free up to 100,000 tool calls a month with three team members, then $29. Composio’s pricing page (checked 2026-10-28, composio.dev/pricing) gives 100K free calls a month only for your own OAuth app or API key; apps on Composio’s shared, managed OAuth get 20K free calls and a per-call surcharge. The login-only route Ben shows is probably the managed one, so his 100K figure may overstate the free allowance for that setup. ^[inferred] Third-party pricing reviews report the paid tiers changed during 2026; check the page before you plan around it.

Interactive connectors open the whole app (added 2026-11-13)

Sources: Anthropic, “Your apps can now open in Claude, and Claude can work in them” (2026-11-10, ai-research/claude-blog-interactive-connectors-full-tool-2026-11-13.md); the same-day framing post (ai-research/claude-blog-more-ways-to-work-sheets-whiteboards-interactive-connectors-2026-11-13.md); Ben AI’s walkthrough (raw/Anthropic_Just_Dropped_4_BIG_Updates_Master_it_in_15_min.md, https://www.youtube.com/watch?v=vyhzL1tW7rE). Full write-up: Claude Sheets, Whiteboards and Data.

  • What changed. Interactive connectors used to show a small live view of a tool in the chat. From 2026-11-10, where a connector supports it, the full tool opens beside the conversation or full screen, and Claude can change the page, row or file you have open while you watch. You approve its actions as you would any connector action.
  • Where. Web and the desktop app, on all plans, rolling out with the new Claude experience. Admins restrict a connector’s tools the same way as before.
  • Which tools. Anthropic names Asana, Canva, Carta, Dropbox, monday.com, Smartsheet, Vercel and Webflow as the starting group, with examples for Adobe, Atlassian (Confluence), Box, HubSpot and Notion. Figma, Harvey and Shopify are building integrations.
  • How it is built. MCP Apps, the open extension that lets an MCP server bring its own interface. Developer support for full apps is in public preview.
  • Ben AI’s use. He opens his team’s Notion content calendar beside the chat and has Claude reorganise the pipeline from a meeting transcript, correcting anything by hand in the same window. He looks for an interactive badge in the connectors directory to find supported apps; Anthropic’s post does not mention a badge.
  • Scale and admin, from the framing post. Claude Marketplace lists more than 9,000 connectors and plugins, including community-built ones. That is not like for like with the 50+ figure at the top of this article (May 2026, connectors only). ^[inferred] Claude auto-connect (beta, eligible Team and Enterprise plans) lets an admin set up an app once so each employee is connected on first use.

Try It

  1. 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.
  2. 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.
  3. 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.