Claude Connectors Hub
Connectors bring external context into Claude and Cowork. This hub explains how connectors relate to MCP and plugins—without inventing a fake app directory.
Availability and the live connector list change in product. Always verify what you can enable in Claude connectors settings and the official Help article below. CoworkHow does not publish a cloned “40+ apps” catalog.
Connectors vs MCP vs plugins
| Building block | What it is | Where to go deeper |
|---|---|---|
| Connectors | Product integrations that let Claude reference external sources (cloud storage, collaboration tools, enterprise data, and more) after you authorize them. | Claude Help: Connectors |
| MCP servers | Model Context Protocol servers—local or remote tool endpoints—often configured in Desktop for custom or developer setups. | Awesome MCP servers · Config generator |
| Plugins | Packaged bundles of skills, connectors, slash commands, and related workflow pieces for a role or industry. | Cowork plugins guide · Finance plugins · Legal plugins |
Plain English: connectors pull context in; skills shape outputs; plugins package both for a job. Full walkthrough: Skills and connectors.
Example connector categories (verify in settings)
These are illustrative categories, not a complete inventory. Names and entitlements vary by plan, workspace admin policy, and partner data agreements.
- Cloud storage — e.g. Google Drive-style file access when connected.
- Collaboration — e.g. Slack or Notion-style workspace references.
- Microsoft 365 — see Connect to Microsoft 365.
- Enterprise / market data — finance blogs and docs mention partner MCP connectors such as FactSet and MSCI; access often needs separate provider entitlements (see finance plugins).
- Legal stack examples — the Legal plugin docs name categories such as Slack, Box, Egnyte, Jira/Confluence, and Microsoft 365; partner CLM/DMS tools may need separate entitlements (see legal plugins).
- Browser — Claude in Chrome and related desktop browser tooling (confirm in product; treat as high-risk for supervised use).
Setup pattern that usually holds: authorize in Claude settings → reference the source in Cowork with a specific prompt → tighten permissions if the task does not need the connector.
Safer defaults
- Connect only the one source the task needs; add more later.
- Prefer read-scoped and least-privilege grants where the product allows.
- Do not treat connectors as “data never leaves your machine”—cloud Cowork sessions and remote processing still apply. See cloud vs local sessions.
- Partner data connectors may require separate subscriptions or API keys; confirm with your provider and admin.
How to enable a connector
The exact screens change as the product evolves, but the working pattern has been stable:
- Open Claude's settings and find the connectors or integrations section — claude.com/connectors is the direct entry point.
- Authorize the source — sign in to the provider account you want Claude to reference and approve the requested access.
- Confirm what was enabled — the connector should appear in your available integrations. If it does not, refresh and check your plan or workspace policy.
- Reference it in a Cowork task — name the source explicitly in your prompt (for example, “use the files in my Drive folder X”) instead of assuming Claude will pick it up on its own.
- Tighten afterward — if the task only needed one folder or one board, narrow the grant or disconnect the connector when you are done.
Step 4 is where most sessions go wrong: a connected source is available, not automatically used. Say what you want Claude to read from.
Permissions, data, and admin controls
- Connectors act through your own account authorization, so Claude can only reach what you could reach — nothing more.
- On team and enterprise plans, workspace admins can restrict which connectors are available. If a connector you expect is missing, ask your admin before troubleshooting your own settings.
- Some partner connectors (market data, document management, legal stacks) require separate provider entitlements. Connecting alone does not unlock paid data.
- Revoking access in the provider's own dashboard (Google, Microsoft, Slack) is the hard off-switch. Removing the connector in Claude settings stops new references, but check the provider side for lasting grants.
When a connector misbehaves
Most connector problems fall into four buckets. Check them in this order:
- Not visible in settings — plan or admin policy may exclude it. Verify your plan on the pricing page, and on managed workspaces ask an admin first.
- Authorized but unused — the session does not know you want it. Name the source in the prompt, or attach the file or folder explicitly.
- Permission errors mid-task — the grant may be narrower than the task. Re-authorize with the access the task needs, or shrink the task to what the grant allows.
- Stale data — a connector may serve a cached or last-synced view. Confirm the source document directly before trusting dates, totals, or statuses.
For protocol-level tool problems — custom MCP servers rather than product connectors — see the dedicated MCP connection failed guide.
Frequently asked questions
Do connectors cost extra?
Core connectors come with the plans that support them, but some partner connectors ride on separate provider subscriptions or entitlements. Treat the provider's own billing as the source of truth before depending on that data in real work.
Can I use connectors in local Cowork sessions?
It depends on where the session runs and what the connector integrates with. Cloud sessions reference cloud sources most directly; local sessions can reach what your machine can reach. The cloud vs local guide breaks down the trade-offs.
Is a connector the same as an MCP server?
No. Connectors are first-party product integrations you authorize in settings. MCP servers are protocol endpoints — often self-hosted — that expose tools and context. Plugins can bundle either. The comparison table above shows where each fits.
Is there a directory of every available connector?
Not on this site, deliberately. The live list changes in product and varies by plan and workspace policy. We explain categories and safer defaults instead of cloning a catalog that would be stale within weeks.
How do I disconnect a connector?
Remove it in Claude's connectors settings, then revoke the grant in the provider's dashboard for a clean removal. Both steps matter if the goal is that Claude no longer has access.