Two tools. Both free. You still can’t run them together on a Claude free account — and neither vendor is the reason why.
If your stack includes any service that isn’t in Claude’s official connector directory, you’re one connector away from a custom connector limit that has nothing to do with pricing. It’s a number Claude keeps, not a bill anyone sends you. And while we were writing this, Anthropic rewrote the help page that explains it.
Two doors into the same protocol
Every connector in Claude reaches you through one of two doors, and which door you’re using matters more than what’s on the other side of it.
The directory is Claude’s own curated list. Gmail, Google Drive, Notion, Slack, Canva, Airtable, Shopify, Stripe, Make, Supermetrics, Windsor.ai — you find these under Customize > Connectors, or from the “+” button in a chat, and adding one is a click and an OAuth screen. Anthropic has reviewed what’s in the directory; the “verified” or “community” label on a listing describes how thoroughly the connector was checked, not how it behaves once you’ve granted it access.
A custom connector is a remote MCP server you point Claude at yourself, by URL, under Customize > Connectors > Add custom connector. Nobody has to have submitted it anywhere. If a vendor hasn’t built a directory listing — or if what you’re connecting is your own internal tool — this is the only door available.
Some tools you’d expect on a curated list simply aren’t there. As of 26 August 2026, Metricool, X and Kit all sit outside Claude’s directory, so adding any of them means going through the custom-connector door regardless of what the tool costs. We’ve been through that door ourselves for a server that isn’t in this book’s twenty at all: Meta’s own ads connector, which we added by URL and then used to count its tools one by one.
The rule, and where we read it
Free accounts are limited to one custom connector at a time. That’s Anthropic’s own wording, and on 26 August 2026 it appears on two separate help centre pages: the general connectors guide and the custom connector guide. Both say the same thing: “Free users are limited to one custom connector.”
The rule applies to any server you add — read-only or not, free or paid on the vendor’s side. The ceiling isn’t about money and it isn’t about the vendor. It’s a count Claude keeps, and it stops at one.
Paid plans — Pro, Max, Team, Enterprise — support more than one at a time. Anthropic doesn’t publish a number for them, so we’re not going to invent one.
Practically, this means you can’t run Metricool and Kit side by side on a free account, even though both are free to connect on the vendor’s side and neither one bills you anything. You can have one of them switched on, or the other, or a Meta Ads connector — never two, until you either remove one or move off Free.
One thing we haven’t tested, and won’t claim: what the interface actually does when you try to add a second one. Anthropic documents the limit but not the failure mode, and we didn’t reproduce it, because reproducing it means downgrading a paid account we need intact for other measurements. A blocked addition is the easy case. The harder case — a connector that appears to add and then quietly returns nothing — is one we’ve measured elsewhere, and until someone hits this ceiling on a free account and reports what they saw, we’re leaving it open rather than assuming the friendly version.
The page changed while we were checking it
This part is the reason we’d tell you not to plan a stack from a documentation page — including the ones linked above.
On 24 August 2026 we recorded the opening line of Anthropic’s general connectors guide. It described web connectors as available to users on the paid plans — Pro, Max, Team and Enterprise — with desktop extensions available to everyone. Read literally, that meant a free account couldn’t use Gmail, Notion or any directory connector at all. It also sat oddly against a second Anthropic page describing free accounts using connectors without that restriction, and against every third-party guide we cross-checked.
Two days later, the same line on the same page reads differently: web connectors are now described as available for all users, across Claude, Cowork, Claude Desktop and mobile. The custom connector section spells out that free accounts are included and capped at one. The disagreement resolved itself — not because anyone settled a debate, but because the page was rewritten.
We’re not reporting this as a gotcha. Documentation gets corrected, and a corrected page is better than an uncorrected one. We’re reporting it because of what it costs you if you’d built around the earlier version: forty-eight hours is shorter than most people’s planning cycle, and there was no notice, no changelog entry, and no reason for a reader who checked on Monday to go back and check again on Wednesday.
What we’d tell you to actually do: open Customize > Connectors on your own account and see what the “+” button offers before you build around any written version of this rule. The account is the one surface no help page controls — and it’s the only one that updates at the same moment your access does.
Why this ceiling matters more than it looks like it should
One connector sounds like a rounding error. It isn’t, for one specific reason: it’s the only ceiling in our connector coverage that has nothing to do with which vendor you pick.
Every other limit we’ve measured — a source count that collapses from ten to one, a single destination licence, a free tier with a day-31 cliff — is a decision one company made about its own product, and you can shop around it by choosing someone else. This one can’t be shopped around. It doesn’t matter whether the tools you need are all free, all cheap, or all expensive. On a free Claude account you get one custom server, and the fix isn’t a different vendor. It’s a different Claude plan.
That’s the part worth planning around before you build anything. If your stack needs two or more services that only exist as custom connectors — which, for marketing and creator tooling specifically, is common — a free Claude plan was never going to hold that stack, independent of what any of those services individually cost.
Directory or custom: sort your stack before you build it
| Where it lives | How you add it | Slot on Free |
|---|---|---|
| Directory (Gmail, Notion, Slack, Canva, Airtable, Shopify, Stripe, Make, Supermetrics, Windsor.ai, and most others) | One click, OAuth screen | Doesn’t count against the limit |
| Custom connector (Metricool, X, Kit, and any vendor server not yet in the directory) | Paste a URL under “Add custom connector” | Counts — one at a time on Free |
Directory membership moves, so check the list rather than trusting ours: we’ve already counted the directory once and found gaps where people assumed coverage existed. Before you plan a stack, sort every connector you’re considering into one of these two piles, then count the custom pile. Zero or one on Free: you’re fine. Two or more: you’re not — not because of anything any vendor charges, but because of a number Claude keeps that has nothing to do with them.
This is one page of a bigger map. The Claude MCP Playbook is one page per connector: what it does, what it really costs, what breaks — plus the plan ceilings that sit above all of them and the decision tree that tells you which stack survives which plan. Join the waitlist.
You Might Also Like
Related Posts
