Skip to content
English

Switch theme

// How-to · Connect tools to agents (MCP, CLI, auth)

Too many MCP tools filling the context window

Every connected MCP server puts the name, description and parameter schema of all its tools into the context. The more servers you connect, the less room is left for the task and the more often the model picks the wrong tool.

verified 2026-10-101 official sources

Scenario: Connect tools to agents (MCP, CLI, auth) →

Symptoms

  • A large share of the context is used before you type anything
  • The agent calls unrelated tools, or responses get slower and more expensive

Common causes

  • Many rarely used servers are enabled globally
  • A single server exposes dozens of tools with long descriptions

How to fix

  1. Configure MCP per project and enable servers only where they are needed instead of globally
  2. Use the client’s tool allow-list or disable switches to keep only the tools the task needs
  3. Put servers behind an MCP gateway or aggregator (e.g. MetaMCP, ContextForge) and expose only a subset per use case
  4. For simple actions (reading files, running tests, git) let the agent use the command line directly instead of another MCP server
  5. Compare servers of the same kind in our software library and prefer the one with fewer, focused tools

Official references

Compiled from official documentation and public discussions on 2026-10-10; not yet reproduced in our own environment. Follow the official docs if they differ.

Data updated: Problems & errors