The MCP Folly: More Context Isn't Always Better
The Model Context Protocol (MCP) is the latest trend in AI engineering. Overusing it is a fast track to context pollution and agent inefficiency.
2025-11-24
Loading content...
The Model Context Protocol (MCP) is the latest trend in AI engineering. Overusing it is a fast track to context pollution and agent inefficiency.
Connecting every possible tool and data source to your AI agent via the Model Context Protocol (MCP) often degrades performance by polluting the context window with distracting noise. Treat MCP as a precision instrument: use it for specialized tasks that need strict access control or deep domain expertise, and keep the rest of your context lean so the agent stays focused.
The biggest mistake engineers are making right now with AI agents is assuming that more context always leads to better results.
We are seeing a rush to connect every possible data source to every agentic workflow. While the Model Context Protocol (MCP) makes this technically easy, and Anthropic does love a protocol they've built themselves, it often creates more problems than it solves. For the majority of users, a crowded context window is just noise that degrades the model's ability to reason.
When you fill an agent's "brain" with every Slack message, Jira ticket, and GitHub PR related to a project, you aren't making it smarter. You are making it distracted.
At its core, the Model Context Protocol is an open standard that allows developers to build secure, two-way integrations between their data and AI models. It removes the need to write custom "glue code" for every new tool you want your agent to use. Anthropic designed it to provide three primary types of interfaces:
It is important to view MCP for what it is: a temporary patch in the rapid evolution of intelligent agents.
Right now, we need MCP because models are still learning how to navigate the messy reality of fragmented data. We are manually building the bridges that the AI isn't yet capable of building itself. The next generation of models will likely render these manual protocols obsolete.
Future AI systems will not need a standardized protocol to "understand" how to interact with a database or a web service. They will possess the inherent agency to interpret interfaces on the fly. Relying too heavily on a rigid protocol today is building on top of a foundation that is already shifting.
This is not to say that MCP is useless. There are specific, high-value scenarios where it remains the correct architectural choice:
For most day-to-day coding and productivity tasks, you are better off keeping your context lean. Don't let your agent get lost in the noise of a thousand integrations. Focus on giving it the right information at the right time.