AI AgentsExplainer
What Is MCP, and What It Costs Before You Ask Anything
MCP is the standard way to connect an AI assistant to your tools. I counted what my own setup brings into a session: 721 tools from 19 servers, against 58 in the example Anthropic published.
5 min read

MCP, the Model Context Protocol, is an open standard that lets an AI assistant use external systems such as email, a code repository or a database. A system is wrapped once as an MCP server, and any assistant that speaks the protocol can call it. Anthropic introduced it in November 2024.
MCP, the Model Context Protocol, is the open standard that lets an AI assistant use your email, your repository or your database. You have probably met it as a settings page in Claude, Cursor or VS Code: a list of servers with a switch next to each. The switch takes a second. The cost is harder to see, so I counted it on my own machine.
One wrapper instead of many
Before MCP, every pairing of an assistant and a system needed its own integration. Anthropic published the protocol on November 25, 2024, as an open standard. A system is wrapped once, as a server, and every assistant that speaks the protocol can use it. In December 2025 Anthropic donated MCP to the Agentic AI Foundation, a fund under the Linux Foundation, so it now sits with a vendor-neutral body.
How one request works
There are three parts. The model decides which tool to call and runs nothing itself. The client is the application you work in, and it carries the calls. The server is a separate program that knows how to reach one system.
Say I ask for the email with my train tickets.
- The client has already told the model which tools the mail server offers.
- The model picks the search tool and fills in its arguments.
- The client sends the call to the server.
- The server searches the mailbox and returns a list of messages.
- The model reads the list and answers me in plain text.
A local server is an ordinary process that the client starts on your machine. In one of my clients, Antigravity, local servers have often dropped on my machine, and I had to reconnect them. When a tool goes missing, I check the process and the sign-in before I blame the model.
Check the date on anything you read
This article describes specification version 2026-07-28. That release changed how a connection starts. A client used to open a session with a setup exchange before it could do anything. Now there are no sessions: each request carries its own protocol version, and every server must offer a discovery call that lists what it supports. A client and a server built for different versions work together only if one of them supports both.
Many popular explainers still describe the old design or name no version at all. The next release is set for March 30, 2027. If a guide to MCP has no date and no version number, treat it as out of date.
The context bill
To call a tool, the model must know its name, its description and the shape of its arguments. That text goes into the context window before your first question.
Anthropic gave an example in November 2025: five servers with 58 tools used about 55,000 tokens before the conversation started. The GitHub server alone accounted for 35 tools and about 26,000 tokens.1 The figure is a year old, so I use it only as a per-tool yardstick.
I counted my own setup in Claude Code. One working session has 721 tools available from 19 servers. A single server declares 265 of them.
| Anthropic's example | My session | |
|---|---|---|
| Servers | 5 | 19 |
| Tools | 58 | 721 |
| Tokens if every definition loads | about 55,000 | 200,000 to 680,000, my estimate |
| Tokens that load in practice | all 55,000 in that example | 11,000 to 14,000, my estimate |
The first estimate multiplies 721 tools by a per-tool cost. Anthropic's example works out to between 740 and 950 tokens per tool. A reader who ran the measurement in Claude Code got about 280. That puts the full load between 200,000 and 680,000 tokens. Even the low end fills a 200,000-token window.
The session works because the client defers loading. It puts only tool names into the context and fetches a full definition when the model asks for that tool. The names are not free either. My list runs to 43,000 characters, which I estimate at 11,000 to 14,000 tokens in every conversation.
Check whether your client does this. In Claude Code the /context command shows how much of the window tools occupy. If a client loads every definition up front, a handful of servers takes a quarter of the window, and a setup like mine does not fit.
What the protocol does not decide
In early November 2026 the German hosting company Mittwald disclosed that a breach of 56 customer projects came through an MCP server it operates. It took the server offline.2 By the company's own account, the server was the entry point. Mittwald has not said what the flaw was.
MCP defines how a tool is declared and called. What a caller is allowed to do with it is up to each server.
That makes every server a question of trust. A mail server reads other people's text and hands it to the model, and that text can contain instructions aimed at the model. A server from an unknown author sees the same data. Its code may be open, but nobody rereads it on every update.
So I have one rule. I connect servers published by the owner of the service, and I do not connect third-party ones that can read or collect my data. In the settings the two kinds look identical.
Where to start
Connect one server to one project. Count the tools it declares and check what they take from your window. Then switch off every server you have not used this week.
I started with 721 tools and a bill I had never looked at. Yours is one command away.
Footnotes
Correction, 20 November 2026: The lower bound of the estimate for loading every tool definition was reduced from 530,000 to 200,000 tokens after a reader measured about 280 tokens per definition in Claude Code.
Sources
- Introducing the Model Context Protocol, Anthropic
- MCP joins the Agentic AI Foundation, MCP blog
- MCP specification 2026-07-28, changelog
- A More Predictable Release Cycle for MCP, MCP blog
- Introducing advanced tool use on the Claude Developer Platform, Anthropic
- Alleged AI-aided cyberattack exploits assistant interface to breach German web host, The Record
- Mittwald Traces a Breach of 56 Customer Projects to Its MCP Server, Webhosting.today
Vladimir Beskorovainyi, Enterprise AI Architect & CTO, author of the Amazon bestseller "Enterprise AI: The KATA Way", founder of Besk Tech (besk.tech)
More in this section
AI AgentsExplainer
What Is an AI Agent, and How Often Is It Right
An agent is a language model in a loop with tools. I measured what that loop is worth on 1,534 questions, and the result explains why I still check every answer.
Get new articles by email
One message when something new is published. No other mail, and you can stop at any time.
The address is used for this one letter and nothing else. Privacy