Connectors
Link Claude to the tools you already use, and let it read your real data instead of whatever you remember to paste. Slack, Google Drive, GitHub, Microsoft 365, Zapier, and a growing list of others.
Connectors are how Claude reaches outside itself to access your data. Instead of you exporting a CSV, pasting it into the chat, and explaining what it is, you say "look at last week's Slack messages in #incidents" and Claude goes and reads them. The data stays where it lives. Claude comes to it.
How they work
Every connector is built on the Model Context Protocol (MCP), an open standard that provides a secure bridge between Claude and external services. When you connect a tool, Claude acts on your behalf using your credentials. It can only access data you already have permission to see in the source system.
Delegated access. Your permissions, Claude's speed.
The connector catalogue
Connectors fall into three tiers based on your plan. Click between the tabs to see what is available at each level.
Available connectors by plan
Google Workspace (all paid plans)
- Gmail: search and read emails, draft messages (cannot send), manage labels, access attachments.
- Google Calendar: view, create, update, and delete events. Find mutual availability. Set recurring meetings.
- Google Drive: search and retrieve docs, add docs to chats via URL, view permissions and change history, save generated files to Drive.
Microsoft 365 (Team and Enterprise plans)
- SharePoint: search across your tenant. Read documents.
- OneDrive: retrieve and read files.
- Outlook: read emails and calendar events. Read-only: cannot send, modify, or delete.
- Teams: read chat conversations. Read-only.
Work accounts only. Personal @outlook.com accounts are not supported.
Developer tools (varies by plan)
- GitHub: access repos, manage issues and PRs, review code.
- Slack: search channels and DMs you have access to. Pull messages into conversations.
- Sentry: error tracking and monitoring data.
- Linear: issue tracking and project management.
Cloud and business (remote MCP, varies)
- Zapier: connect 8,000+ apps. Execute workflows (send emails, update CRMs, schedule meetings).
- Atlassian: Jira and Confluence for project history, task status, knowledge base.
- Asana: project management data.
- Intercom: customer conversation history.
- Cloudflare: infrastructure and security data.
- Square, PayPal, Plaid: financial transaction data.
- Notion, Stripe, Figma: partner-built integrations.
The list is growing fast. Visit claude.com/connectors for the latest.
How to set one up
Check with your admin. On Team and Enterprise plans, an admin needs to enable connectors for the organisation before individual users can connect. On personal plans, you can set them up yourself.
Open the connectors directory. Go to Customize, then Connectors (or type "/" in any chat and select Connectors). Click "+" to browse.
Authenticate with your own credentials. Each connector asks you to log in with your real account for that service. This is how the delegated permission model works: Claude gets your access level, not an admin's.
Use it in a chat. Once connected, just ask. "Find the proposal Jo shared in Drive last Tuesday" or "summarise the #incidents Slack channel this week". Claude will use the connector automatically when the question calls for it.
What it looks like in practice
Manual data pasting vs connector access
You spend five minutes finding and pasting messages. You miss two threads. Claude summarises what you gave it, not what actually happened. The summary is incomplete because the input was incomplete.
Claude reads the channel directly via the Slack connector, including threads you would have missed. Produces a structured summary in about ten seconds. Decisions in one section, blockers in another, with timestamps and names.
Enterprise considerations
Admin controls and restrictions
- Org owners and primary owners enable connectors organisation-wide. Individual users still authenticate separately.
- Admins can restrict specific actions (read-only, write/delete prevention) across the entire organisation.
- Connectors only work in private projects on Team and Enterprise plans, not in shared chats.
- Synced content cannot be shared across chats on Team and Enterprise.
- For Microsoft 365, admins can use Microsoft Entra controls for deeper restriction (revoking specific OAuth scopes).
- Enabling a connector makes it available to all org members. There is no per-group connector control at this time.
Limitations to know about
- Read-only for most. Microsoft 365 and Gmail drafts cannot be sent. Most connectors retrieve data rather than modify it.
- Your permissions are the ceiling. Claude cannot access data you do not already have access to in the source tool. If you cannot see a Slack channel, neither can Claude.
- Text-only for Google Workspace. Images embedded in Docs or Sheets are not processed. Text content only.
- Data encrypted in transit and at rest. Not used for model training.
- Growing fast. The catalogue changes frequently. Check claude.com/connectors for the latest list.
Connectors are the bridge between "Claude is smart but does not know my data" and "Claude knows what I know". Start with the one connector that touches your most-used data source, and expand from there.
Next: Cowork is Claude running multi-step jobs on your desktop. Or go back to the Tools hub.