MCP Connector Costs: The Four Patterns Behind Every Surprise Bill

Almost every MCP connector is free. That sentence is true, and it is also the reason people end up with a bill they did not plan for.

The connector is a doorway. What costs money is the room behind it — the plan of the product it reaches into, the metered operations it quietly triggers, or the trial capacity it was built on before that capacity shrank. Anthropic says Claude’s connector directory now lists more than 950 MCP servers, so checking them one at a time is not a strategy. Reading the pattern is.

We connect these for a living. Every connector in our MCP directory has been set up in a real account, and four of them are on our card right now. There are only four ways an MCP connector can cost you money. Learn to spot which one you are looking at, and the bill stops being a surprise.

The four cost patterns

Pattern 1 — Free, and it stays free

The connector rides on a product that is genuinely free for one person. Gmail, Google Drive, Google Calendar, Slack, Notion. You connect it, you use it, and nothing ever happens to your card.

The risk here is not financial, and it is worth naming anyway: these are the connectors that touch your most personal data, and several of them can write, not just read. Free and safe are different questions. This chapter answers the first one.

Pattern 2 — Free tier with a cliff

The connector is generous on day one and much smaller on day thirty-one. This is the pattern that catches people, because nothing breaks at signup. It breaks weeks later, once you have already built something on capacity you no longer have.

Windsor.ai is the clearest example we have tested. The free trial gives you ten data sources for thirty days. The permanent free plan that follows gives you one. We connected GA4 and Instagram during the trial, then added Meta Ads and Pinterest — four sources on a plan that will hold one. Nobody will bill us for that. The plan will simply shrink underneath us, and three of the four connections will stop returning data.

The failure mode of Pattern 2 is a broken workflow, not an invoice. That makes it worse, not better. An invoice at least tells you what happened.

Pattern 3 — Free connector, paid host

The MCP costs nothing. The plan you need in order to have anything for it to read costs plenty.

Supermetrics is the honest version: the connector is free, and the Starter plan we needed in order to keep using it runs €59.78 a month with European VAT included, or roughly $68 — one destination, one data source, one user. Canva is the softer version: the connector is free and works fine on the free plan, right up to the monthly AI generation credits. We hit that ceiling often enough that we are now on Pro at €12 a month, roughly $14. The connector never changed. Our volume did.

Shopify belongs here too, and it is the one people misread most often. The connector is free and official. It is also useless without an active store plan, because an empty store has no orders for Claude to read.

When you evaluate a Pattern 3 connector, the question is never “what does the MCP cost.” It is “what is the cheapest plan of this product that makes the MCP worth having.”

Pattern 4 — Metered

You pay per unit, and the unit is invisible until it isn’t. X is the version most people meet first: pay-per-use API, no free lane. Automation platforms like Zapier and Make meter tasks and operations, and a single instruction to Claude can fire a great many of them.

The trap inside this pattern is that metered costs can hide behind a free connector. Windsor.ai looks like a way to read X data without paying for X. It isn’t. Connecting X through Windsor asks you for four X developer credentials, which means you are supplying your own paid X API access and Windsor is riding on top of it. We found that out by trying it. A free connector stacked on a metered API is still a metered API — the bridge does not absorb the toll.

Metered pricing is not bad pricing. It is the only pattern where the bill reflects how much you actually used, which is fair. It is also the only pattern where the bill can grow while you sleep, and that earns a ceiling before it earns your trust.

Five traps

1. The day-31 cliff

You build during a trial, you plan around trial capacity, and the plan quietly stops being possible a month later.

The complication is that day thirty-one is not a fixed date. It is a date the vendor can move. Our Airtable trial expired on schedule and the workspace dropped to the free plan on its own: no warning, no charge, nothing broken, just a small grey badge where the plan name used to be. Later the same day, an email offering to extend the trial by two weeks. We declined, because we were not using the paid features. But the mechanism is worth naming — the cliff you wrote in your calendar is not necessarily the cliff you get, and an extension resets the date in your head without resetting the risk.

Note also what that downgrade cost us, which was nothing. Two small bases, well inside the free ceiling, still working. That is the honest shape of this trap: it hurts in proportion to what you built on top of it. Someone running live automations wakes up to stopped automations.

What to do: the day you connect anything with a trial, write the expiry date somewhere you will actually see it — not inside the tool, which is the thing that will stop working. If the vendor extends it, move the date instead of deleting it. Then answer one question in advance: if this drops to the free tier tomorrow, what breaks?

2. The free connector on a paid product

Pattern 3 in practice. You read “MCP included at no additional cost,” you connect it, and the real price of the setup turns out to be the subscription you now have to keep.

What to do: price the cheapest plan that makes the connector useful, not the connector.

3. Metered operations you cannot see

One instruction to Claude — “clean up this table and update every row” — can become dozens of operations on an automation platform. The instruction feels like a single action. The meter disagrees.

We are running that measurement now on Zapier and Make, and we will publish the numbers when we have them rather than guess at them today.

What to do in the meantime: before pointing Claude at a metered platform, run one small task and check the meter afterwards. You are not testing whether it works. You are calibrating how many units a sentence costs.

4. Pay-per-use without a ceiling

Usage-based pricing has no natural stopping point and no built-in “that’s enough.”

What to do: set a spending cap in the vendor’s dashboard before the first call. Not after the first bill.

5. Auto-recharge — the cost that is on no pricing page

This is the one we learned the expensive way, on our own account, in July 2026.

Credit-based billing systems frequently ship with auto-recharge switched on by default and no cap set. The balance never runs out, so nothing ever fails, so nothing ever tells you that your consumption has changed. The mechanism designed to prevent an interruption is the same mechanism that prevents you from noticing.

What to do, before you connect anything metered: open billing settings, turn auto-recharge off, and set a hard monthly limit. If you would rather leave auto-recharge on, set the cap anyway. It takes ten seconds and it is the single highest-value thing on this page.

Three stacks, three monthly bills

Patterns are only useful if they add up to a number. Here is what three realistic setups actually cost. We pay in euros with EU VAT included, so the dollar figures are approximate conversions of real invoices, not list prices.

The solo creator stack has everything Claude needs to draft, organise, schedule and file, and it costs nothing. The only reason to spend is Canva Pro, and only once you are hitting the AI generation ceiling often enough to be annoyed by it.

The e-commerce operator adds Stripe and Shopify. Both connectors are free, you are already paying for the store, and Stripe takes its cut per transaction. No new subscription enters your life because of MCP.

The marketer is where “my AI setup is free” stops being true. Windsor’s paid tier starts at $19 a month billed annually and sets the floor; Supermetrics anchors the ceiling. It is worth knowing in advance that this jump is caused by analytics, not by Claude.

The one rule

Before connecting anything, answer two questions.

Which of the four patterns is this? And what happens on day thirty-one?

If you cannot answer the second one, you have not finished evaluating the tool.

You Might Also Like

More from our tested guides on connecting Claude to the tools you already pay for.