Guide
We checked 279 business tools for a Claude connector. Most have none.
We catalogued the business software teams actually ask Claude to act inside, then checked the real state of each tool's connector. Re-verified against Anthropic's directory in July 2026: official coverage is growing fast, and the gap is still wide where it hurts most.
As of July 2026, across 279 business tools teams want Claude to work in, 179 of them, or 64 percent, have no connector at all, down from 77 percent in June as Anthropic's directory grew past 400 connectors. The other 100 have official, read-limited, or third-party connectors with standard toolsets, and the gap remains total in vertical, custom, and most ERP software.
Key takeaways
- We catalogued 279 business tools and re-verified each against Anthropic's connector directory in July 2026. 179, or 64 percent, have no Claude connector at all.
- Coverage is moving fast: a month earlier the figure was 77 percent. Roughly 50 of these tools gained an official directory connector in a single month.
- The gap has not moved where it matters most: every vertical-industry tool we track (43 of 43) and every custom or in-house system (5 of 5) still has no connector, and ERP is barely touched (10 of 11).
- For covered tools, the question has shifted: official connectors ship a standard toolset, so the gap is now depth, custom fields, and gated write actions shaped to your workflow.
How many business tools actually have a Claude connector?
Of 279 business tools we catalogued, 179 have no Claude connector at all as of July 2026. That is 64 percent. The remaining 100 split into official directory connectors with standard toolsets, read-limited connectors, and third-party options. Coverage that both reads and writes deeply, shaped to a specific team's workflow, still is not something any of them ship out of the box.
We grouped each tool by the state of its current connector. The split looks like this:
- No connector at all: 179 tools, 64 percent. Nothing exists to connect Claude to the tool.
- Directory connectors: 66 tools, 25 percent. An official connector is listed in Anthropic's directory, with a standard, fixed toolset.
- Read-limited: 28 tools, 11 percent. A connector exists, but it reads or does very little.
- Third-party only: 6 tools, 2 percent. The only option is a third-party or data-vendor connector.
The headline is the first line. For more than six in ten of the business tools teams actually run, there is still no way to connect Claude at all without building one. And for the tools that have something, the something is a general-purpose toolset rather than the specific actions a team's workflow needs.
How fast is the connector gap closing?
Fast at the head, not at the tail. Between our June and July 2026 counts, roughly 50 tools gained an official directory connector as Anthropic's directory grew past 400 entries, dropping no-connector coverage from 77 percent toward the low 60s. But the newly covered tools are overwhelmingly mainstream SaaS. Vertical, custom, and ERP software barely moved: the 15 vertical tools we added to the catalog in late July, from dental practice management to auto repair, arrived with no connector at all, which is why the headline figure sits at 64 percent.
This is the most useful thing the two snapshots show. The directory is adding mainstream names quickly: payments, marketing platforms, developer tools, HR suites. If your stack is popular horizontal SaaS, the odds a basic official connector exists improved meaningfully in a single month.
The tail did not move. Vertical industry software went from 28 uncovered tools to 28. Custom and in-house systems from 5 to 5. ERP moved by exactly one (NetSuite gained an official connector). The economics explain it: a vendor ships one connector for its million-user product, but nobody ships one for the practice-management system a single industry runs, and nobody ever will for your in-house tools.
Does any tool ship deep read-write out of the box?
Increasingly, official directory connectors include write actions, and that is real progress. What none of them ship is depth shaped to your team: coverage of your custom fields and objects, workflow-specific actions, and approval gates on the writes you consider risky. Official connectors are standard by design. Deep, shaped read-write access remains something you build, not something you turn on.
A standard toolset is useful for answering questions and handling common actions, but real work runs through the specific way your team uses the tool: the custom fields on the deal, the required approvals before anything sends, the objects your admin added. The moment Claude needs to act inside that shape, a generic connector runs out.
What deep read-write means here
Separate read and write tools mapped to your account's real usage, custom fields and objects included, with destructive actions like delete and send gated behind a confirmation you approve. That is the bar the standard connectors, official ones included, stop short of.
Which categories have the biggest connector gap?
The gap is total in vertical and industry software (43 of 43 with nothing) and custom or in-house tools (5 of 5), and near-total in ERP and operations (10 of 11). It is smallest in project management, storage, and marketing, where official directory coverage concentrated. The pattern is consistent: horizontal, popular software gets covered; industry-specific software does not.
Sorted by how many tools have nothing at all, the gap is widest here:
- Vertical and industry software: 43 of 43 have no connector.
- Custom and in-house: 5 of 5 have no connector.
- ERP and operations: 10 of 11 have no connector.
- E-commerce: 13 of 16. Scheduling: 8 of 10. Forms and surveys: 8 of 11. E-signature: 7 of 10.
- HR and payroll: 10 of 15. Help desk: 8 of 13. CRM: 10 of 18. Email: 10 of 18.
The best-covered categories tell the same story from the other side. Project management (7 of 21 uncovered), storage and files (4 of 11), and marketing (10 of 21) are exactly the horizontal categories a directory reaches first. The work tools where teams most want Claude to act, and the industry systems where whole verticals live, are exactly where coverage still is not.
Why do so many business tools have no connector?
Most business software lives in the long tail. Vertical platforms, ERPs, and in-house systems each serve a slice of one industry, so no vendor ships a general connector for them, and the directory's fast growth concentrates on mainstream SaaS instead. Even for covered tools, standard toolsets ship first because generic is easier than shaped. Deep, workflow-specific access is the work nobody does by default.
The catalog skews toward that long tail. The largest groups are vertical and industry software (28 tools), databases and data (23), project and work management (21), and marketing (21). These are not the handful of apps everyone integrates. They are the specific systems a given team runs, which is exactly the software a general connector directory skips, and the July snapshot confirms it: a month of rapid directory growth left the vertical column untouched.
The pattern holds inside covered tools too. Official connectors expose the standard objects and common actions, because that generalizes across every customer. Your custom fields, your approval rules, and your team's specific write actions do not generalize, so they stay uncovered until someone builds for them directly.
What does it take to close the gap for a specific tool?
Closing the gap means building a custom connector for the one tool you run: separate read and write tools mapped to its real API and your real configuration, authenticated as your own account, with destructive actions gated behind your confirmation. It is scoped to the actions you need, not a generic set, so Claude can do the actual work in that tool rather than just read from it.
Whether a tool sits in the 64 percent with nothing or among the covered tools whose standard connector runs out at your workflow's edges, the fix is the same shape: a connector built and maintained for your tool and your configuration, with deep read-write and human-in-the-loop controls on the risky actions.
How we counted
We catalogued the business tools teams ask us to connect Claude to, then classified each tool's current connector as none, read-limited, directory-basic, or third-party. The July 2026 figures were re-verified July 24 to 27 against the full Anthropic connector directory, then 405 connectors across 17 pages, with ambiguous name matches checked against each connector's detail page. The set is business software, not consumer apps, and it grows as we add tools: 15 vertical tools joined the catalog on July 27, each verified against the directory before listing.