Connectors Available for Claude: Google Drive, Slack, Notion, and More
This page lists the connectors currently supported for Claude's enterprise search: Google Drive, Slack, Notion, SharePoint, Confluence, GitHub, Jira, and Salesforce.
Note: this is a generic reference list rather than a ranked checklist or decision guide - use it to see at a glance what each connector covers before deciding which ones to connect first.
How to Use This List
- Skim the descriptions below to see which connector matches the kind of content your team asks about most.
- Most organizations connect more than one source, since documents, chat, and tickets each live in a different tool.
- Start with whichever source answers the most common questions your team already asks Claude manually.
- Revisit this list periodically, since Anthropic and MCP-based integrations both continue to expand over time.
Document & File Sources
- Google Drive - Claude can search files, folders, and shared documents stored in Drive, which makes it useful for finding written reports, spreadsheets, and planning docs without knowing the exact file name in advance.
- SharePoint - similar to Drive, SharePoint holds documents and files within a Microsoft-centric organization, so this connector is the natural fit for teams whose file storage lives there instead of Drive.
Chat & Collaboration Sources
- Slack - Claude can search messages and channels, which is useful for surfacing decisions, discussions, or context that only ever got written down in a Slack thread rather than a formal document.
- Notion - Claude can search pages and databases in Notion, which suits teams that use it as a wiki or knowledge base for plans, specs, and living documentation.
- Confluence - Confluence serves a similar role to Notion inside many organizations, holding wiki-style pages and documentation, so this connector covers teams standardized on Atlassian's tools.
Code & Engineering Sources
- GitHub - Claude can search code, issues, and pull requests, which is useful for answering questions about how something was implemented, what a bug report said, or the status of a pull request.
- Jira - Claude can search tickets and issue tracking data, which helps surface the status, history, or details of specific work items without manually digging through a board.
CRM & Business Sources
- Salesforce - Claude can search CRM records, which is useful for questions about accounts, opportunities, or customer history that would otherwise require opening Salesforce directly.
Choosing Where to Start
- If most questions are "what did we decide?" - start with Slack and Notion, since decisions and their rationale often live in chat and wiki pages.
- If most questions are "where is the document for X?" - start with Google Drive or SharePoint, depending on which one your organization actually uses.
- If most questions are engineering-specific - start with GitHub and Jira together, since code context and ticket status are usually asked about in the same breath.
- If most questions are customer or account-specific - start with Salesforce.
FAQs
Do I need to connect all eight sources at once?
No. Most teams start with one or two connectors that match their most common questions, then add more over time.
Are these connectors first-party or MCP-based?
Some are first-party, built and maintained directly by Anthropic, and others may be reached through MCP-based integrations depending on the tool. Both types work the same way from a search perspective.
What does Claude actually search inside Slack?
Messages and channels the connector has been authorized to see, which is why the permission scope granted during setup determines what is actually searchable.
What does Claude actually search inside GitHub?
Code, issues, and pull requests within the repositories the connector has access to.
Can Claude see everything in my Google Drive once connected?
Only what the connector's permission scope allows, which is usually set to specific folders rather than an entire account.
Why would a team connect both Notion and Confluence?
Some organizations use both tools for different purposes, or are mid-migration from one to the other, so connecting both avoids gaps in searchable knowledge.
Is Salesforce data treated any differently from document sources?
The underlying mechanics are the same: Claude searches whatever the connector's scope exposes and cites the specific record it used, whether that record is a CRM entry or a document.
Will more connectors be added to this list over time?
Likely yes, since both first-party connectors and the MCP ecosystem continue to expand, so this list should be treated as current at time of writing rather than fixed forever.
Who decides which connectors get enabled for a team?
This is typically an IT or admin decision, made after auditing the scope and access each connector would require.
Does connecting a source mean it is searched automatically for every question?
No. Claude decides whether a connected source is relevant to a given question and only searches it when that source is likely to help answer it.
What happens if two connected sources disagree?
Claude can surface both, citing each source separately, which often makes the discrepancy itself the most useful part of the answer.
Where should I go to actually connect one of these tools?
The getting-started basics page walks through connecting your first source, and the step-by-step guide covers Slack and Notion specifically.
Related
- Enterprise Search & Connectors Basics - a hands-on guide to connecting your first source.
- First-Party vs MCP-Based Connectors: What's the Difference - how these connectors are built and maintained.
- Connecting Slack and Notion to Claude Step by Step - a walkthrough for two of the connectors listed here.
- Understanding Connector Permission Scopes and Data Access - how scope limits what any connector can see.
Stack versions: Written against the Claude model lineup current as of ~June 2026 - Claude Fable 5, Claude Opus 4.8, Claude Sonnet 5 (the default), and Claude Haiku 4.5. Model names, pricing, and product features move quickly - verify current specifics at platform.claude.com/docs before relying on them.