Best Claude Connectors for Business (2026)
Guide · · Published November 2026 · 9 min read
By Ashwin Gopinath, CEO
TL;DR
The best Claude connectors for a business team cover the apps where work happens: Google Drive and Gmail or Microsoft 365 for documents and mail, Slack for conversation, HubSpot or Salesforce for customers, Linear, Jira or Asana for work tracking, Granola or Fireflies for meetings, and Zapier for everything else. Each connector gives Claude live access to one app, so none of them remembers what the company decided across apps or shares it with teammates' Claude sessions and other agents. That is the job of one memory connector: Sentra, the managed organization memory for teams and AI agents, served over MCP, which you add to Claude as a custom connector. Owners on Team and Enterprise plans add connectors for the organization and set each tool to Always allow, Needs approval or Blocked.
What are Claude connectors, and which plans can use them?
A connector "links Claude to an outside app or service, such as your calendar, your documents, or your issue tracker" (claude.com). Under the hood, connectors are MCP servers: Anthropic's directory is "a catalog of MCP servers that work across all Claude products", including claude.ai, Claude Desktop, Claude Mobile, Claude Code and Cowork (directory). Anthropic launched the directory on 14 July 2025 with partner-built connectors for tools such as Notion, Canva and Stripe (claude.com).
- Plans. Custom connectors added by URL work on Free, Pro, Max, Ultra, Team and Enterprise, with one custom connector on Free (docs). Some directory connectors have their own limits: Gmail is available on Pro, Max, Ultra, Team and Enterprise, while Microsoft 365 is available on every plan.
- Team and Enterprise. An Owner adds a connector for the organization, and each member then connects with their own account, so Claude sees only what that person can see in the app.
- Where they run. Claude on the web gets remote connectors, the desktop app adds local connectors, and mobile gets remote connectors. Connectors added in claude.ai are automatically available in Claude Code (Claude Code docs), and Cowork loads the ones enabled for your account.
Anthropic does not publish a count of connectors in the directory, so treat numbers quoted elsewhere as estimates.
Which Claude connectors should a business team install first?
Install connectors for the apps Claude must read or act in, one job at a time. Every connector below except Sentra, which you add as a custom connector, appears in Claude's directory as Anthropic verified, and each was checked on Anthropic's and the vendor's own documentation on 16 November 2026.
| Connector | Job | What Claude can do | Built by | Docs |
|---|---|---|---|---|
| Sentra | Shared company memory | Ask what was decided, what changed, who owns what and what is at risk, across email, Slack, meetings, tickets and CRM, with sources and each person's permissions | Sentra (added as a custom connector) | Sentra for Claude |
| Google Drive, Gmail, Google Calendar | Documents, mail, schedule | Find and read files, mail and events; Gmail is read-only and cannot create, send or modify emails | claude.com | |
| Microsoft 365 | Documents, mail, schedule, Teams | Work with Outlook mail and calendar and Teams messages; send or draft only where administrators turn on write actions | Anthropic | claude.com |
| Slack | Conversation | Read channels and threads, start conversations and add reactions | Slack | docs.slack.dev |
| HubSpot | CRM | Read and write contacts, deals and engagements | HubSpot | developers.hubspot.com |
| Salesforce | CRM | Listed in the directory as a beta of the Salesforce Headless 360 MCP Server | Salesforce | Claude directory listing |
| Linear | Work tracking | Read and write issues and projects | Linear | linear.app |
| Atlassian (Jira and Confluence) | Work tracking and docs | Search, summarise and update Jira and Confluence through the Rovo MCP Server | Atlassian | atlassian.com |
| Asana | Work tracking | Access the Asana Work Graph of tasks and projects | Asana | developers.asana.com |
| Notion | Wiki and docs | Find answers in the workspace, turn notes into documents, manage projects | Notion | developers.notion.com |
| Box | Files | Search and use Box files over OAuth | Box | developer.box.com |
| Granola or Fireflies | Meetings | Search meeting notes and transcripts and pull out action items | Granola; Fireflies | docs.granola.ai |
| Intercom | Support | Find and retrieve conversations and contacts | Intercom | developers.intercom.com |
| Stripe | Payments | Work with the Stripe API and search Stripe's knowledge base (public preview) | Stripe | docs.stripe.com |
| Zapier | Everything else | Take actions in the apps Zapier connects | Zapier | zapier.com |
Pick by job, not by count. A sales team gets most from the CRM, mail and meetings connectors; an engineering team from Linear or Jira, Slack and docs; a finance team from Drive or Microsoft 365 and Stripe. Canva, Figma and monday.com also have verified connectors for design and project work.
How do I add a connector that isn't in the directory?
Any remote MCP server can be added as a custom connector by URL (docs). On individual plans, open Customize, then Connectors, select Add, then Add custom connector, and paste the server URL. On Team and Enterprise plans an Owner adds it under Organization settings, then Connectors, then Add, then Custom; on Enterprise, a member whose custom role includes managing the organization's libraries can add it too. Each member then signs in once, so the server sees that person's permissions.
In Claude Code, a remote server is one command. This is the one for Sentra:
claude mcp add --transport http sentra https://api.sentra.app/mcp/Run /mcp in a Claude Code session to authorize it. Our guide to connecting Claude to organizational memory over MCP covers each client and the admin rollout.
How do admins control what connectors can do?
- Per-tool permissions. Owners on Team and Enterprise plans can limit which actions a connected service can take across the organization, setting each to Always allow, Needs approval or Blocked (support.claude.com). A sensible default is reads on Always allow and writes on Needs approval.
- Roles on Enterprise. A newly created role defaults to Needs approval on every connector (support.claude.com).
- Labels. Verified means Anthropic tested the connector's tools for quality and compatibility, which Anthropic says is not a security audit. Community connectors are screened but not reviewed in depth. Custom connectors are ones you added yourself, which Anthropic has not reviewed (docs).
- Per-person access. Members connect with their own accounts, so a connector never shows Claude more than the person could open in the app.
For the wider policy questions, such as what an agent may do with data once it has it, see our guide to AI agent permissions.
Why don't connectors alone give Claude company context?
Each connector answers from one app at the moment someone asks. Ask Claude what the company agreed with a customer, and it has to search Gmail, Slack, the CRM and the meeting notes, then guess which of four slightly different answers is current. Ask again tomorrow, or ask from a teammate's account, and it does the same work again, possibly with a different result.
- One app per connector. Nothing joins a decision in a meeting to the CRM record and the Slack thread that changed it.
- No memory across sessions or people. What Claude works out in one person's chat does not reach a colleague's Claude, Claude Code or another agent.
- Every answer re-reads the sources. That costs tokens and time on every question.
A memory connector closes that gap. Sentra reads the same apps continuously, records each fact with its source and when it became true, and serves the current answer to every person's Claude, to Claude Code and to any other agent over MCP. Claude's own Projects and memory stay useful for individual work; our guides to Claude memory for teams and MCP memory servers compare the options.
For the controls a security lead should require before connectors reach company mail and files, permission inheritance, approval on actions and audit, see AI agent access control.
FAQ
Are Claude connectors free?
Connectors are a feature of Claude plans: custom connectors work on every plan, with one on Free, and some directory connectors such as Gmail need a paid plan. Some connected services charge for their own product or API, and the work Claude does counts toward your plan's usage.
How many connectors are in the Claude directory?
Anthropic does not publish a count. The directory covers connectors built by vendors such as Google, Slack, Notion, Atlassian, HubSpot, Asana, Linear and Stripe, plus Anthropic's own Microsoft 365 connector, and any remote MCP server can be added as a custom connector.
Are Claude connectors MCP servers?
Yes. Anthropic's directory is a catalog of MCP servers, and a custom connector is any remote MCP server you add by URL. The same servers work in claude.ai, the desktop and mobile apps, Claude Code and Cowork.
Do connectors work in Claude Code and Cowork?
Yes. MCP servers added in claude.ai are automatically available in Claude Code, and Cowork loads the connectors enabled for your account. In Claude Code you can also add a remote server directly with claude mcp add.
Is it safe to connect Slack or Google Drive to Claude?
Each member connects with their own account, so Claude sees only what that person can see, and on Team and Enterprise an Owner can set each tool to Always allow, Needs approval or Blocked. Start with read access on Always allow and put any write or send action on Needs approval. The Verified label means Anthropic tested quality and compatibility, not that it audited security.
Which Claude connectors should you pick?
Pick connectors for the apps Claude must read or act in, and set writes to Needs approval. Then add one memory connector, so what the company decided is shared across every teammate's Claude, Claude Code and your other agents instead of being rebuilt in each chat. The Sentra for Claude page shows what Claude gets from it.
To see Claude answer from your own email, Slack and meetings, with the source behind each answer and each person's permissions applied, book a demo.