One measurement puts a 50-server tool catalog at 56 percent of a 128K context window before the first prompt. The per-server arithmetic is the part worth budgeting.
Reality
- Evidence34
- Adoption
- Insufficient
- Hype gap+44
- Incentives86
- Confidence38
A developer measured 111,713 tokens of JSON schema from 10 MCP servers, injected before the first message, and priced the year at $1,764 per seat. The per-server number is the useful one.
Reality
- Evidence26
- Adoption29
- Hype gap+58
- Incentives88
- Confidence47
A dev.to benchmark says one connector carries 42 percent of the schema load while supplying 3.7 percent of the tools. The direction holds. The money math does not.
Reality
- Evidence26
- Adoption12
- Hype gap+58
- Incentives82
- Confidence44
One developer's count of a five-server Claude Code setup holds up where you can check it and drifts where you cannot. The checkable part is enough to change how you connect tools.
Reality
- Evidence32
- Adoption10
- Hype gap+55
- Incentives82
- Confidence30
An engineering diary for a small MCP client puts numbers on schema bloat in the context window and on the roughly 950 hand-written lines it took to ship with zero dependencies.
Reality
- Evidence30
- Adoption10
- Hype gap+20
- Incentives65
- Confidence33