The 10 Best Claude Connectors in 2026 What Each Can Actually Do

Claude connectors use the Model Context Protocol (MCP) to link Claude to your apps. Top connectors in 2026 include OnceHub for scheduling with external guests, Google Calendar for personal schedule management, Google Drive for document research, Slack for thread summaries, Gmail for inbox triage, and Figma, Linear, and GitHub for product work. Free plans allow one custom connector.

Quick Comparison: The 10 Best Claude Connectors

How We Chose These Connectors

We evaluated connectors based on write capabilities (action taking vs. passive reading), setup effort, plan accessibility across Anthropic tiers, enterprise permission controls, and measurable workflow time savings.

Most people do not have a prompting problem. They have a context problem.

Claude is capable, but by default it has no idea what is in your calendar, your Drive, or your repository. So the workflow becomes: search for the data, copy it, paste it into Claude, get an answer, copy that, paste it back into the app you started in.

That round trip is the actual bottleneck, and connectors are what remove it.

What Claude connectors actually are

A connector links Claude to an external service through the Model Context Protocol, an open standard for letting AI tools read from and write to other software.

The distinction that matters is read versus write. Some connectors only let Claude look at your data. Others let it do things: update a page, create an issue, book a meeting. The second group is where the time savings are, and it is also where you want to pay attention to permissions.

Two types exist, and the difference affects setup.

Directory connectors are listed in Anthropic's Connectors Directory, labelled as verified or community, and connect in a couple of clicks. Custom connectors are any remote MCP server you add by URL, which covers anything not in the directory. According to Anthropic's documentation, custom connectors work on Claude, Claude Desktop, and Cowork across Free, Pro, Max, Team, and Enterprise plans, with Free users limited to one.

One technical detail worth knowing before you start: when you add a custom connector, Claude reaches your MCP server from Anthropic's cloud infrastructure rather than from your local machine. That is true on claude.ai, Claude Desktop, Cowork, and mobile. Consequently, your server must be reachable from the internet, and servers behind a VPN or corporate firewall require Anthropic's IP addresses to be allowlisted.

Category 1: Scheduling and calendar

Calendar connectors can put an event directly on your own calendar. What standard calendar tools do not do is book an external guest the way a scheduling platform does: against the exact availability, buffers, and booking rules you publish, while capturing guest information.

1. OnceHub: best for booking meetings autonomously

OnceHub offers two integration options depending on your workflow. The OnceHub Directory Connector connects via OAuth for broad scheduling management (listing calendars, fetching booking links, managing upcoming meetings, processing cancellations, and asking guests to reschedule). For autonomous AI agents, the OnceHub Platform MCP Server provides dedicated tools to verify live availability and write confirmed bookings.

The problem it solves: A standard calendar connector can check when you have free time, but it cannot verify whether a time slot respects your published booking rules or buffer settings. OnceHub enforces these rules before writing the booking.

How it works. The OnceHub Platform MCP server exposes get_booking_time_slots, which returns availability with your buffer settings and busy times from connected calendars applied, and schedule_meeting, which accepts the guest's name, email, location, start time in ISO 8601, and time zone in IANA format.

Because availability and booking both run through OnceHub's own scheduling engine, the booking is checked against the same rules that produced the slot, rather than being written blind to a calendar. We explain why that architecture matters in our guide to double booking.

Realistic prompts: "Find a thirty-minute slot next week for a demo with Sarah (sarah@acme.com)" for autonomous booking, or "Cancel my 3pm meeting with Daniel and send him a reschedule request" using the directory connector.

Setup note: Add OnceHub directly from the Claude Connectors Directory using OAuth. For developer agents using the Platform MCP Server, connect via API key as detailed in the OnceHub MCP getting started guide.

2. Google Calendar: best for reviewing your schedule

Google Calendar's connector is best for managing your own calendar: reviewing your schedule, blocking focus time, or moving internal meetings. It is available directly in the Connectors Directory with OAuth setup.

The problem it solves: you plan a project with Claude and it cheerfully schedules deep work on a Tuesday where you already have five hours of meetings.

Giving Claude visibility into your schedule lets it prepare agendas, summarize upcoming commitments, and create or adjust internal events. When a meeting involves an external guest who needs to book on your published rules, pair it with OnceHub.

Category 2: Documents and knowledge

This is where most people start, because it is the category where the copy-paste tax is highest.

3. Google Drive: best for research across documents

Drive is probably the highest-value connector for anyone whose work context lives in documents rather than in code. It lets Claude search your files, open several at once, and compare them.

The problem it solves: the answer is spread across a dozen Docs and Sheets, and assembling it by hand takes longer than the analysis.

A prompt like "find the last three quarterly reports and summarize the revenue differences" goes from a twenty-minute task to a single request. Anthropic maintains connector-specific guidance and known issues for Google Drive, Gmail, Slack, GitHub, Google Calendar, and Microsoft 365 on their Connectors Overview page.

4. Notion: best for knowledge management

Notion's connector covers both directions, which is what makes it useful rather than merely convenient. Claude can search your workspace and also update pages in it.

The problem it solves: project documentation drifts out of date because updating it is nobody's favorite task.

The pattern that works well: let Claude read scattered meeting notes across the workspace and turn them into a weekly progress summary, written back into the page where your team already looks.

5. Microsoft 365 and SharePoint: best for corporate environments

If your organization runs on Microsoft, this is the connector that matters, covering OneDrive, Outlook, and Teams. It does the same job as the Google connectors for the other half of the enterprise world.

The problem it solves: your context is in SharePoint and Outlook, and no amount of Drive integration helps.

Worth checking the connector-specific requirements before deployment, since Microsoft tenants vary considerably in how they handle third-party access.

Category 3: Team communication

Communication tools hold an enormous amount of context that nobody has time to read. These two connectors are less about generating output and more about recovering information you already have but cannot find.

6. Slack: best for thread summaries

Slack is where decisions get made and then immediately lost. The connector lets Claude read specific channels and reconstruct what was actually decided.

The problem it solves: a forty-message thread contains one decision and three action items, and finding them means reading all forty messages.

Beyond summarizing, Claude can identify who owns which task and draft replies with the thread's context already in hand. This is the connector most people underestimate before they try it.

7. Gmail: best for inbox triage

The Gmail connector gives Claude access to search, draft, send, reply to, and forward emails, asking for explicit approval before sending by default.

The problem it solves: manually rebuilding email context inside a chat window takes longer than just writing the reply yourself.

The useful applications are triage rather than composition: surfacing what actually needs attention, finding the thread where something was agreed, and drafting responses that reference what was already said.

Category 4: Product, development, and design

These three share a pattern. Each one replaces a description of your work with the work itself, which is the difference between Claude guessing at your conventions and following them.

8. Figma: best for design-to-code

Figma's connector gives Claude access to the design file itself rather than a picture of it. That difference shows up immediately in the quality of the code it writes.

The problem it solves: asking Claude to write CSS from a screenshot produces code that approximately resembles the design and matches none of its actual values.

With access to layouts, components, and variables, Claude writes implementation code against real spacing, real tokens, and real component structure rather than inferring them from pixels.

9. Linear: best for product management

Linear's connector suits teams that want Claude involved in planning rather than just execution. It reads issues, projects, and cycles.

The problem it solves: working out what is actually blocking the sprint means opening fifteen tickets and holding them in your head.

Claude can review open issues, surface recurring blockers, and suggest what to prioritize next. The real gain is turning a specification into structured tickets in one pass instead of an afternoon.

10. GitHub: best for codebase context

GitHub's connector is the one most developers install first, and for good reason. It gives Claude your actual file structure rather than whatever you remembered to paste.

The problem it solves: code suggestions that ignore your conventions, your dependencies, and the way your project is actually organized.

Claude can read repositories, review pull requests, and plan implementations that fit the codebase as it exists. Combined with Linear, it closes the loop from ticket to implementation.

How to install Claude connectors

The steps differ depending on whether the connector is in the directory and whether you are on a personal or organization plan.

Adding a directory connector

Open Customize > Connectors (or click '+' in the chat box > Connectors > Manage connectors). Browse the Connectors Directory, select the connector, and complete OAuth authentication.

On Team and Enterprise plans, an Owner adds connectors first under Organization settings > Connectors, and members then connect them from their own settings.

Adding a custom connector

1. For a remote MCP server (such as OnceHub at https://my-mcp.oncehub.com):
2. Go to Customize > Connectors
3. Click + Add, then Add custom connector
4. Enter the remote MCP server URL
5. Review the authentication settings Claude detected and adjust them if your server needs something different, such as a request header carrying an API key
6. Click Add

Anthropic's custom connector guide covers the organization flow and the authentication options in more detail. For a worked example using a bearer token rather than OAuth, the OnceHub MCP setup guide walks through the endpoint, the header, and where to generate the API key.

Adding a connector in Claude Code

For remote HTTP connectors, use the --transport http flag (or --transport sse for SSE endpoints):

claude mcp add --transport http <name> <url>

A common mistake is reaching for the local form, claude mcp add <name> -- npx -y <package>, for a remote connector. That syntax launches a local server as a subprocess and is correct for packages you run on your own machine, not for a hosted MCP endpoint.

Permissions and what to watch

Connectors execute actions on your behalf, which is the point and also the thing to configure deliberately.

Tools ask before they act until you decide

Tools start with permissions requiring confirmation. You can configure each tool to Always allow, Needs approval, or Blocked. Setting read-only tools to "Always allow" while keeping action-oriented tools on "Needs approval" provides a balanced workflow.

You can turn individual tools off

Open the connector in Customize > Connectors and toggle specific tools. Organization owners on Team and Enterprise plans can also establish org-wide action restrictions.

Custom connectors are unverified by definition

Anthropic states this plainly in its documentation: custom connectors let you connect Claude to services that have not been verified by Anthropic. That is not a reason to avoid them, but it does mean the trust decision is yours rather than Anthropic's. Check who maintains the server before you point it at company data.

Organization controls exist

On Team and Enterprise plans, organization owners select available connectors, enforce org-wide permission settings, and enable member connector requests.

Stop copy-pasting, start executing

A disconnected AI is a thinking partner. A connected one is closer to a colleague who can actually do things.

The practical advice: do not install ten connectors on day one. Pick the one that removes the copy-paste you do most often, use it for a week, and add the next only when you hit a real limit. Each connector adds capability and also adds tool definitions to every conversation, so a focused setup usually outperforms a comprehensive one.

Add OnceHub from the Claude Connectors Directory. For developer agents booking autonomously, refer to the OnceHub Platform MCP server guide or explore the source on GitHub.

Frequently asked questions

The questions that come up most often when people set connectors up for the first time.

What are Claude connectors?

Connectors link Claude to external services through the Model Context Protocol, an open standard that lets AI tools read from and write to other software. Rather than pasting data into a chat window, Claude fetches what it needs and can take actions in those systems. They work across Claude, Claude Desktop, Claude Code, and the API, and are available on Free through Enterprise plans, with Free limited to one custom connector.

How do I give Claude access to my calendar?

Connect Google Calendar or Microsoft 365 from the Connectors Directory to let Claude read and manage events on your personal schedule. If you want Claude to handle external guest scheduling (sharing booking links, listing meetings, processing cancellations, or requesting reschedules), add the OnceHub connector. Developers building autonomous agents can use OnceHub's Platform MCP Server to check availability rules before confirming bookings.

Can Claude book meetings for me, not just read my calendar?

Yes. Calendar connectors create events on your own calendar. To book external guests according to published scheduling rules, OnceHub's Platform MCP Server provides get_booking_time_slots and schedule_meeting as separate tools. This workflow ensures availability and buffer times are evaluated before a slot is booked.

Is it safe to connect Claude to my company's Google Drive?

Directory connectors like Google Drive use OAuth, so you sign in to Google and grant specific scopes rather than handing over a password, and you can revoke access at any time. Within Claude, tools from a connector can be individually blocked or set to ask before each use. The bigger consideration is organizational rather than technical: on Team and Enterprise plans, an Owner controls which connectors are available, and that is the right place to set policy rather than leaving it to individual users.

What is the difference between Claude connectors and custom GPTs?

Custom GPTs are configured instructions and uploaded files inside OpenAI's ecosystem. Connectors are built on the Model Context Protocol (MCP), an open standard allowing a single server to function across compatible AI clients. Additionally, MCP connectors emphasize direct read/write tool execution across external systems.

How many connectors should I install?

Fewer than you expect. Every connector's tool definitions occupy context window space before your conversation starts, so a setup with ten connectors leaves Claude less room to work with than one with three. Start with the single workflow where you copy and paste most often, whether that is your calendar, your documents, or your repository, and add the next only when you hit a genuine limit. You can also disable individual tools within a connector to keep only what you use.