TL;DR: Too many mounted MCP servers can consume an agent’s usable context before work begins, according to Archestra. Per-session gating and manifest filtering help keep the exposed tool set within the context budget.
Editorial analysis by NHI Mgmt Group, based on content published by Archestra: “MCP Context Window Too Many Servers: Why 100 MCP Servers Crush Your Agent”.
By the numbers:
- Mounting 20 MCP servers can consume about 240,000 tokens before a user types anything.
Key questions
Q: Why does mounting many MCP servers create risk even when no tool is used?
A: Because the server descriptions, schemas, and hints still consume context on every turn.
Q: What breaks when every MCP server is mounted by default?
A: Least privilege becomes difficult to express, because the agent can see more capability than the current task requires.
Q: What should teams do first when an MCP manifest is too large?
A: Start by measuring the manifest the agent actually receives, not the number of servers on paper.
Practitioner guidance
- Limit the manifest by default Only expose MCP tools required for the current session, role, or task.
- Measure prompt cost before scaling servers Print the manifest the agent actually sees and measure token usage before the first user message.
- Collapse overlapping servers into fewer surfaces Merge duplicate search, lookup, and list functions into shared servers so the agent does not pay repeated schema overhead for the same capability.
Bottom line: Too many mounted MCP servers can exhaust the agent’s usable context before the user’s task even starts.
Glossary terms: MCP Manifest, Context Budgeting, Per-Session Tool Gating, Gateway Manifest Filtering
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Manifest bloat is a governance failure, not just a performance bug. When every mounted server is treated as harmless overhead, teams ignore the fact that capability descriptions are now part of the access surface. In MCP environments, identity, authorisation, and prompt budget collide in the same object. The practical consequence is that access design must account for the cost of merely being present in the session.
A few things that frame the scale:
- 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: How should organisations control MCP tool exposure without rebuilding every server?
A: Use a gateway to filter the manifest centrally, so the agent sees only the tools allowed for that role and session. This is the cleanest option when server sprawl already exists, because it changes the exposed surface without forcing every upstream team to redesign its server.
👉 Read our full editorial: MCP server sprawl can exhaust context before any task begins