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.