Skip to content
Custom Connectors

Guide

What connectors does Claude have? The full landscape

Claude ships with some connectors and a directory adds more, but the coverage is thinner than the marketing suggests. Here is the actual landscape, grounded in a check of 264 business tools.

Updated July 23, 20265 min read

Claude has built-in connectors for a set of mainstream tools plus a directory of listed and third-party connectors, most of them read-leaning or shallow. Across 264 business tools we catalogued, 203, or 77 percent, have no connector at all, and none of the 264 ships full read-write access out of the box.

Key takeaways

  • Claude's connector landscape splits into four states: no connector, read-limited, directory-basic, and third-party only.
  • Of 264 business tools we checked, 203 (77 percent) have no Claude connector of any kind.
  • The 61 tools that have something are all read-limited, shallow, or third-party. None ship full read-write.
  • The gap is total in vertical software, ERP, and custom in-house tools, where every tool we checked has nothing.

What kinds of connectors does Claude have today?

Claude connects to tools through MCP connectors, which come in a few kinds: built-in connectors for mainstream tools, directory-listed connectors you can add, and third-party or data-vendor connectors. In practice each existing connector falls into one of three states: read-limited, directory-basic, or third-party only.

When we catalogued 264 business tools and checked the real state of each one's connector, every tool landed in one of four groups:

  • No connector at all: nothing exists to connect Claude to the tool. 203 tools, 77 percent.
  • Read-limited: a connector exists, but it reads or does very little. 27 tools, 10 percent.
  • Directory-basic: a listed connector exists, but it stays shallow. 18 tools, 7 percent.
  • Third-party only: the only option is a third-party or data-vendor connector. 16 tools, 6 percent.

So the honest answer to what connectors Claude has is: some, for a minority of tools, and the ones that exist stop short of full read-write.

Which tools have the best Claude connector coverage?

Storage and file tools are the best covered, with the fewest tools missing a connector entirely. Mainstream CRM, project management, help desk, and email tools usually have something too, though it leans read-only or shallow. Best covered is relative: even the strongest category leaves more than a third of its tools with nothing.

The existing connectors do real work within their limits. A read-limited connector can answer questions about your data, summarize what changed, and pull records into a conversation. For research and reporting, that is often enough.

But the coverage thins fast outside the mainstream. In the work categories where teams most want Claude to act, the numbers from our catalog are: CRM, 10 of 18 tools with no connector; project management, 12 of 21; help desk, 9 of 13; email, 11 of 18.

What connectors does Claude not have?

The biggest absence is the long tail. In vertical and industry software, ERP and operations, and custom or in-house tools, every tool we checked has no connector: 28 of 28, 11 of 11, and 5 of 5. E-commerce, forms, e-signature, marketing, HR, and accounting are nearly as bare.

This is where most business software actually lives. Vertical platforms, ERPs, and in-house systems each serve a slice of one industry, so no one ships a general connector for them. A connector directory naturally covers the handful of apps everyone uses and skips the specific systems a given team runs.

The result is that the software most central to a company's operations is the software Claude is least likely to connect to out of the box.

Does any Claude connector offer full read-write access?

Not out of the box. Across all 264 tools in our catalog, not one ships a connector that gives Claude full read-write access: separate read and write tools, scoped to your account, with destructive actions gated behind your confirmation. The connectors that exist are read-only, shallow, or third-party.

This matters because reading is only half of any workflow. A read-only connector can tell you about the deal, the ticket, or the record, but it cannot run update_deal, post the reply, or fix the field. The moment you ask Claude to do the work rather than describe it, the built-in options run out.

Where these numbers come from

The figures are from our coverage-gap study: 264 business tools catalogued, each classified as none, read-limited, directory-basic, or third-party based on what exists publicly as of June 2026.

The full breakdown, including the category-by-category numbers, is in the data post linked below.

What do I do if my tool has no Claude connector?

If your tool has no connector, or only a read-limited one, the fix is a custom MCP connector built for that tool: read and write tools mapped to its real API, authenticated as your own account, with destructive actions gated behind your confirmation. That is how full read-write exists today, built, not turned on.

Whether your tool sits in the 77 percent with nothing or the 23 percent with something partial, the shape of the solution is the same: a connector scoped to the actions your workflow needs, inheriting your account's permissions and nothing more.

You can check the current state of a specific tool, and what a full read-write connector for it would unlock, in our connector catalog.

Frequently asked questions

Is an MCP server the same thing as a Claude connector?
Effectively, yes. Claude connects to external tools through the Model Context Protocol, and a connector is an MCP server exposed to Claude with a set of tools it can call. Built-in connectors, directory connectors, and custom connectors are all MCP servers underneath. The difference between them is who built them, what they cover, and whether they can write.
Are more built-in Claude connectors being added over time?
Yes, the landscape moves, and the numbers shift as built-in and directory connectors are added. But the structural pattern has held steady: new connectors lean read-only because reading is lower risk than writing, and they cover mainstream apps while skipping the long tail of vertical, ERP, and in-house software where most business work actually happens.
Why do existing Claude connectors lean read-only?
Because reading data is easier and lower risk than writing it. A read connector cannot break anything, so it is the natural first version to ship. Safe write access is a bigger piece of work: separate write tools, scoping to the user's own permissions, and confirmation gates on destructive actions. That work rarely ships by default, which is why full read-write is built per tool.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.