Connect Claude to the tools your team already uses. Slack, HubSpot, Google Drive, Jira, Salesforce, GitHub, and 30+ more. One-time OAuth setup, scoped permissions, and no data stored on Anthropic's servers.
Built on the open MCP protocol. Works alongside plugins and skills.
A connector links Claude to an external tool. It lets Claude pull data from and take actions inside apps like your CRM, project tracker, email, or file storage. Without connectors, Claude can only work with what you paste into the conversation. With them, it goes straight to the source.
Under the hood, every connector is an MCP server. MCP stands for Model Context Protocol, an open standard created by Anthropic and maintained at modelcontextprotocol.io. It's the same protocol that powers tool use across the Claude ecosystem. Each MCP server exposes a set of actions (like "search contacts" or "create issue") that Claude can call during a conversation.
The key detail: connectors respect your existing account permissions. If you can't access a certain HubSpot deal or Google Drive folder, neither can Claude. There's no elevated access, no admin backdoor. Claude sees exactly what you see.
Setting up a connector takes about 30 seconds.
Launch Claude Desktop and start a Cowork conversation. If you've installed a plugin that requires a connector, Claude will prompt you to authenticate the first time it needs access.
A browser window opens with the standard OAuth flow for that tool. You log in with your existing credentials and approve the specific permissions Claude is requesting. For tools that don't support OAuth, you'll provide an API key instead.
Authentication persists across sessions. You won't need to re-authorize unless you revoke the token or it expires. The connection details are stored locally in your .mcp.json configuration file, not on Anthropic's servers.
Done. Claude can now pull data from and take actions in the connected tool. Ask it to summarize your Slack threads, update a Jira ticket, draft an email in Gmail, or pull a contact list from HubSpot. No limit on how many tools you connect.
Connectors can run as local servers (via stdio) or remote servers (via HTTP). They're configured through .mcp.json files at the user, project, or managed scope. On Enterprise plans, admins can pre-configure connectors and distribute them across the organization through the plugin marketplace.
Every connector listed below is available today in Claude Cowork. New connectors are added regularly as Anthropic and the MCP community build more servers.
Don't see your tool? MCP is an open protocol. We can build a custom connector for any tool with an API.
Your connector setup depends on your tools. Here are the stacks we see most often.
HubSpot or Salesforce for lead management, Google Drive for transaction documents, Gmail for follow-up sequences, Google Calendar for showings and closings.
Cowork for Real Estate →Box or Egnyte for document storage and version control, Jira for matter tracking and deadlines, Microsoft 365 for drafting and collaboration, DocuSign for signatures.
Cowork for Legal →Snowflake or BigQuery for financial data, Slack for team communication, Google Sheets for reporting, HubSpot for client management.
Cowork for Finance →HubSpot for campaigns and contacts, Ahrefs and SimilarWeb for competitive research, Canva for design assets, Klaviyo for email automation, WordPress for content publishing.
Cowork for Marketing →Most connectors take under a minute to set up on your own. But when you're connecting 10+ tools across a team, or you need a connector for a tool that doesn't have one yet, that's where we come in.
We set up all your connectors, test them against your actual accounts, and configure the right scopes so Claude has access to what it needs without overreaching. For Enterprise teams, we pre-configure connectors in the managed scope so every team member gets the same setup.
If your team relies on a tool that doesn't have an official MCP connector, we'll build one. We've created custom connectors for proprietary CRMs, internal databases, and niche SaaS tools. The connector becomes part of your custom plugin package.
A connector gives Claude access to a tool. A plugin or skill tells it what to do with that access. We wire them together so Claude follows your actual workflows, not generic ones.
We run training sessions covering which connectors are active, what Claude can access, and how to manage permissions. Your team leaves knowing how to connect new tools and fix common problems on their own.
Book a free 15-minute call. We'll look at what tools you use and tell you which connectors to set up.
Book a Free 15-Minute CallNo commitment. We'll map your tools to Cowork connectors in 15 minutes.