Claude Connectors

Claude connectors let you bring business context into a conversation and, where a connector supports it, act on that context in the original tool. Your next client brief could draw on email, documents and account records without someone assembling a paste-up first. Start with a recurring read-only job, then add narrowly scoped write actions after the team can review what will change.

What Claude Connectors Actually Do

A connector gives Claude a route into an application. Its available tools determine whether Claude can search, read, create or change something. Connecting a service does not make every operation in that service available. Check its directory listing for supported actions and availability. Anthropic’s connector overview.

Think of a connector as a service desk with a menu: finding a document and sending a message are different requests, with different consequences. The important admin decision is which requests to permit.

There are two starting points:

• Directory connector: choose a listed service and complete its connection flow.
• Custom connector: supply the address of a remote MCP server, a hosted program that exposes selected tools and data to Claude.

MCP, short for Model Context Protocol, is the shared connection format underneath custom connectors. Read What Is MCP? for the components, or its MCP vs API comparison for why an MCP server can sit in front of an existing software interface.

Which Claude Plans Allow Connectors?

Custom connectors using remote MCP are available on Free, Pro, Max, Team and Enterprise. Free is limited to one custom connector. Anthropic lists support on Claude, Cowork and Claude Desktop. Custom connector availability.

The Enterprise role exception appears in Anthropic’s remote MCP setup guide. These plan rules do not establish that every directory service is available to every account. Check the service’s own requirements, including permissions in the application you want to connect.

Turn On a Directory Connector

Use this settings route from Use connectors to extend Claude’s capabilities:

1. Open Customize > Connectors.
2. Select the + beside Connectors.
3. Browse by category or through the full list.
4. Select your connector.
5. Read its description and capabilities.
6. Select Connect or Install.
7. Complete the authentication prompts.
8. Adjust any service-specific settings or permissions.

For Team and Enterprise, an Owner or Primary Owner first opens Organization settings > Connectors, selects Browse connectors at the bottom, chooses the service and selects Add to your team. Members then authenticate through the connection flow above.

Organization enablement and account authorization are separate. The standard flow uses individual sign-in; Anthropic also documents Enterprise-managed authentication in beta for Team and Enterprise, which can provide access automatically at first login. Organization connection options.

To use a connected service in a chat, select + at the lower left, or type /, hover over Connectors, and turn on the relevant service. Conversation controls.

Add a Custom Connector From a Remote MCP Server

Get the actual MCP endpoint from the service operator. A website homepage is not a substitute for that endpoint. OAuth is the authorization flow used to sign in and grant access; an OAuth client identifies Claude to the server handling that authorization. Custom connector configuration.

Start With the Correct Entry Path

The two help pages give these entry paths:

Sources: general connector instructions and remote MCP instructions. Keep the distinction when writing your internal rollout guide. Anthropic also notes that the configuration dialog can vary by organization. Dialog variations.

Complete the Configuration in This Order

After entering through the appropriate path:

1. Enter the connector’s display name.
2. Enter its remote MCP server URL, then select Continue.
3. Review the detected authentication settings, adjust them if required, then select Continue.
4. Under Authentication, choose Sign in now, Sign in when needed, or No sign in.
5. Under OAuth client, choose Use Claude’s published identity (Recommended), Register automatically, or Use your own OAuth client. This setting is absent when you choose No sign in.
6. Under Request headers, add the server’s required fixed credentials, such as an API key or bearer token, if it uses that authentication method.
7. Select Add. Complete the connection process where required.

Request-header authentication is currently beta and limited to some organizations. If that section is missing, your organization may not have access. Request-header availability.

This is the field sequence in Anthropic’s remote MCP help page; the authentication reference explains the choices. Use the server operator’s configuration instructions to select among them.

After an owner adds a connector, members open Customize > Connectors, find it and select Connect. It usually carries a Custom label, though a matching directory domain can display the service’s branding instead. Then enable it in the conversation. Member setup.

Check Where the Connection Comes From

A remote connector calls your server from Anthropic’s cloud, including when you use Claude Desktop or Cowork. A server reachable only from your laptop or company VPN is therefore insufficient. The direct connection must be reachable from Anthropic’s infrastructure; the help page describes firewall allowlisting for private-network deployments. Give that network requirement to the person hosting the server before troubleshooting the chat. Remote connector network requirements.

Three Concrete Business Setups

These are proposed workflows, not signed-in tests or measured results. Choose the setup closest to where your team already keeps its work.

Google Workspace: Client Briefs for an Agency

An account manager could connect Gmail, Google Calendar and Google Drive, then ask Claude to prepare for a client meeting using recent correspondence, the meeting details and the current project document.

A useful request: “Prepare a brief for tomorrow’s Acme meeting. Separate agreed commitments, unresolved questions and decisions we need. Link the source for each commitment.” The manager reviews the brief before using it with the client.

Anthropic documents email search, calendar access and Drive retrieval. Gmail also supports drafting and sending, with approval before sending by default. Keep the first workflow focused on the brief, then consider a reviewed follow-up draft. Gmail attachment content is not available through that connector, so an attached proposal may need another route. Google Workspace capabilities and limitations.

The payoff is less preparation spent hunting through separate sources, especially for managers who handle several accounts.

Microsoft 365: Project Briefs for a Delivery Team

A project lead could use the Microsoft 365 connector to collect relevant Outlook correspondence, SharePoint or OneDrive documents, and Teams discussions into a delivery brief. Ask for blockers, changed commitments and the source behind each change.

The setup has an additional prerequisite: a Microsoft Entra Global Administrator must grant tenant consent. It requires a Microsoft Entra tenant tied to a Microsoft Business plan; personal Microsoft accounts do not qualify. Team and Enterprise also need Claude organization enablement. Microsoft 365 is listed as available on Free, Pro, Max, Team and Enterprise. Microsoft 365 setup.

For the first rollout, use retrieval to prepare the review meeting. Sending email, changing files or using other write tools requires the updated Microsoft permission consent and write-tool enablement. That is a separate admin decision, not an automatic consequence of connecting search. Microsoft write-tool requirements.

Notion, Slack and a CRM: Account Briefs for Customer Success

A customer success team could combine its Notion playbook, relevant Slack conversations and a customer relationship management system, or CRM, to prepare a renewal brief. Use a suitable directory CRM connector if its exposed tools fit; otherwise have a developer provide a narrow remote MCP server for account lookup and approved note updates.

Notion’s listing includes search and content editing. Anthropic’s Slack search documentation specifies Team and Enterprise and requires the Slack app installation first. Treat those as service-specific checks, not a promise that every Slack connection has the same setup. Notion connector, Slack search connector.

A useful request: “Compare this account’s renewal risks with our playbook. Show supporting messages and records, identify missing evidence, and draft the account note for review.” The proposed custom server should expose only the account records and write operations this workflow needs. Building that server still requires implementing the actual product operations and authentication. Building connectors.

Six Uses, Ranked by Business Payoff

The strongest starting point is account preparation: it recurs, crosses tools and ends in a reviewable document. These are the uses I would prioritize, subject to the connector’s actual tools and permissions.

Measure the consequence in reviewed output, not the number of connections. For an illustrative pilot, suppose a manual brief takes 30 minutes and a connector-assisted brief takes 10 minutes including checking sources. Across six briefs a week, that would save two hours. Those are planning assumptions, not measured Claude performance. Record your own before-and-after time, corrections and missing sources.

Safety Checks Before Connecting a Tool That Can Write

Treat read access and write access as separate decisions. A connector that can fetch a document may also expose tools that send messages, edit records or delete data. Review the server operator and the requested permissions before authorizing it. An unlisted connector can connect to a service Anthropic has not verified. Custom connector security.

Use this rollout checklist:

1. Verify the operator and endpoint. Get the URL from the service’s own documentation or your responsible developer. Identify any intermediary that receives business data.
2. Inspect the account and permissions. Limit access to what the workflow requires. If an organization connector uses a shared API key, everyone using it receives that key’s access, rather than an individual account boundary. Credential behavior.
3. Set the tool policy before rollout. The help page’s owner controls are Customize > Connectors > select the connector > Tool permissions. For a category or individual tool, choose Always allow, Needs approval or Blocked. Start write/delete tools at Blocked, then move only the required actions to Needs approval. Organization tool restrictions.
4. Review the proposed change. In your pilot, check the destination, recipients, affected records and final content before approving a write. A prompt saying “be careful” should not substitute for permission controls.
5. Watch retrieved instructions and server changes. Prompt injection means hostile instructions embedded in content or tool output. Treat that content as evidence to evaluate, not authority to grant another action. Review behavior again when the connector’s tools change. Server security guidance.
6. Disable external write tools for Research. Anthropic warns that Research can call connector tools without further approval and explicitly advises disabling tools that write to external applications. Research with custom connectors.

Two Things Worth Building

A connector is useful infrastructure. The sellable product is a reliable recurring outcome. These opportunities use estimated monthly US Google searches from DataForSEO, checked on 15 October 2026. They indicate interest in the broader job, not demand for a particular Claude implementation.

The strongest opportunity is a reviewed CRM update assistant. A sales operations lead could pay for account notes that arrive with the supporting evidence and a clear proposed change. The query “crm automation” has an estimated 590 monthly searches. A small first version would support one CRM, one account lookup and one note-update action, with review and an activity record. The catch is matching evidence to the correct customer and preventing duplicate or conflicting updates. A generic connector alone does not solve those problems.

An internal answer assistant is the second opportunity. An operations lead could pay for answers from maintained procedures, linked to their sources and owners. “ai knowledge base” has an estimated 880 monthly searches. Start with one department’s approved Notion pages or document collection, source links and a clear route for unanswered questions. The catch is stale or contradictory material: someone still owns the policies, permissions and corrections.

The CRM idea has the clearer acceptance test: did the right, approved note reach the right record? Knowledge answers can be valuable, but their quality depends on the source collection staying useful.

What Connectors Do Not Fix

A successful connection does not prove that an answer is complete or a proposed update is correct. Test with known questions, missing records and ambiguous account names before relying on the workflow.

Service limitations still matter. For example, the Google connector documentation excludes Gmail attachment content and images embedded in retrieved Drive documents. Build your pilot around the information the connector can actually return. Google limitations.

My recommendation: use connectors first where a person can inspect a brief or draft. For a fixed, unattended workflow, compare an ordinary application integration before making a conversational assistant responsible for execution.

Does Claude Pro allow connectors?

Yes. Pro supports custom remote MCP connectors. Use the Pro/Max entry path above, then check the chosen service’s own account and permission requirements. Anthropic’s setup guide.

What connectors should I use with Claude?

Start with the tools that hold evidence for one recurring task: Gmail and Drive for an agency brief, Microsoft 365 for a project review, or Notion and an appropriate CRM connection for account preparation. Add another only when it supplies information or an action that the workflow needs.

Is it safe to use connectors in Claude?

Safety depends on the service operator, credentials, exposed tools and your approval policy. Start with narrow read access, inspect proposed changes and monitor tool behavior. A trusted service can still contain material that should not be treated as instructions.

Can I use the Gmail connector in Claude?

Yes. Anthropic lists Gmail connectors for all Claude and Claude Desktop users. Team and Enterprise require organization enablement before individual authentication. Gmail supports reading and drafting as well as sending with approval by default. Google Workspace guide.

Your Monday move: pick the account manager who prepares the same brief every week. Connect the minimum relevant sources, keep writes disabled, and compare a sourced draft with the manual brief. Expand only after the reviewer can explain what was retrieved, what was missed and which proposed action deserves permission.

If you want this workflow built around your team’s tools and approval rules, explore AI automation.