The Mannequin Context Protocol (MCP) is genuinely helpful. It provides individuals who develop AI instruments a standardized strategy to name features and entry knowledge from exterior programs. As an alternative of constructing customized integrations for every knowledge supply, you possibly can expose databases, APIs, and inner instruments by means of a typical protocol that any AI can perceive.
Nevertheless, I’ve been watching groups undertake MCP over the previous yr, and I’m seeing a disturbing sample. Builders are utilizing MCP to rapidly join their AI assistants to each knowledge supply they will discover—buyer databases, help tickets, inner APIs, doc shops—and dumping all of it into the AI’s context. And since the AI is sensible sufficient to kind by means of an enormous blob of information and select the elements which are related, all of it simply works! Which, counterintuitively, is definitely an issue. The AI cheerfully processes large quantities of information and produces affordable solutions, so no person even thinks to query the method.
That is knowledge hoarding. And like bodily hoarders who can’t throw something away till their houses change into so cluttered they’re unliveable, knowledge hoarding has the potential to trigger severe issues for our groups. Builders be taught they will fetch much more knowledge than the AI wants and supply it with little planning or construction, and the AI is sensible sufficient to cope with it and nonetheless give good outcomes.
When connecting a brand new knowledge supply takes hours as a substitute of days, many builders don’t take the time to ask what knowledge truly belongs within the context. That’s how you find yourself with programs which are costly to run and unimaginable to debug, whereas a whole cohort of builders misses the prospect to be taught the essential knowledge structure expertise they should construct sturdy and maintainable purposes.
How Groups Be taught to Hoard
Anthropic launched MCP in late 2024 to provide builders a common strategy to join AI assistants to their knowledge. As an alternative of sustaining separate code for connectors to let AI entry knowledge from, say, S3, OneDrive, Jira, ServiceNow, and your inner DBs and APIs, you employ the identical easy protocol to offer the AI with all kinds of information to incorporate in its context. It rapidly gained traction. Firms like Block and Apollo adopted it, and groups in all places began utilizing it. The promise is actual; in lots of circumstances, the work of connecting knowledge sources to AI brokers that used to take weeks can now take minutes. However that velocity can come at a value.
Let’s begin with an instance: a small staff engaged on an AI instrument that reads buyer help tickets, categorizes them by urgency, suggests responses, and routes them to the precise division. They wanted to get one thing working rapidly however confronted a problem: They’d buyer knowledge unfold throughout a number of programs. After spending a morning arguing about what knowledge to tug, which fields had been vital, and how you can construction the combination, one developer determined to only construct it, making a single getCustomerData(customerId) MCP instrument that pulls the whole lot they’d mentioned—40 fields from three completely different programs—into one huge response object. To the staff’s aid, it labored! The AI fortunately consumed all 40 fields and began answering questions, and no extra discussions or choices had been wanted. The AI dealt with all the brand new knowledge simply nice, and everybody felt just like the challenge was heading in the right direction.
Day two, somebody added order historical past so the assistant may clarify refunds. Quickly the instrument pulled Zendesk standing, CRM standing, eligibility flags that contradicted one another, three completely different identify fields, 4 timestamps for “final seen,” plus total dialog threads, and mixed all of them into an ever-growing knowledge object.
The assistant stored producing reasonable-looking solutions, whilst the information it ingested stored rising in scale. Nevertheless, the mannequin now needed to wade by means of hundreds of irrelevant tokens earlier than answering easy questions like “Is that this buyer eligible for a refund?” The staff ended up with a knowledge structure that buried the sign in noise. That further load put stress on the AI to dig out that sign, resulting in severe potential long-term issues. However they didn’t understand it but, as a result of the AI stored producing reasonable-looking solutions. As they added extra knowledge sources over the next weeks, the AI began taking longer to reply. Hallucinations crept in that they couldn’t observe all the way down to any particular knowledge supply. What had been a extremely helpful instrument grew to become a bear to take care of.
The staff had fallen into the knowledge hoarding entice: Their early fast wins created a tradition the place individuals simply threw no matter they wanted into the context, and finally it grew right into a upkeep nightmare that solely received worse as they added extra knowledge sources.
The Abilities That By no means Develop
There are as many opinions on knowledge structure as there are builders, and there are normally some ways to unravel anyone drawback. One factor that nearly everybody agrees on is that it takes cautious decisions and many expertise. Nevertheless it’s additionally the topic of a number of debate, particularly inside groups, exactly as a result of there are such a lot of methods to design how your software shops, transmits, encodes, and makes use of knowledge.
Most of us fall into just-in-case considering at one time or one other, particularly early in our careers—pulling all the information we would probably want simply in case we’d like it relatively than fetching solely what we’d like once we really need it (which is an instance of the other, just-in-time considering). Usually once we’re designing our knowledge structure, we’re coping with instant constraints: ease of entry, dimension, indexing, efficiency, community latency, and reminiscence utilization. However once we use MCP to offer knowledge to an AI, we are able to typically sidestep a lot of these trade-offs…quickly.
The extra we work with knowledge, the higher we get at designing how our apps use it. The extra early-career builders are uncovered to it, the extra they be taught by means of expertise why, for instance, System A ought to personal buyer standing whereas System B owns cost historical past. Wholesome debate is a crucial a part of this studying course of. By all of those experiences, we develop an instinct for what “an excessive amount of knowledge” appears to be like like—and how you can deal with all of these tough however essential trade-offs that create friction all through our tasks.
MCP can take away the friction that comes from these trade-offs by letting us keep away from having to make these choices in any respect. If a developer can wire up the whole lot in just some minutes, there’s no want for dialogue or debate about what’s truly wanted. The AI appears to deal with no matter knowledge you throw at it, so the code ships with out anybody questioning the design.
With out all of that have making, discussing, and debating knowledge design decisions, builders miss the prospect to construct essential psychological fashions about knowledge possession, system boundaries, and the price of transferring pointless knowledge round. They spend their childhood connecting as a substitute of architecting. That is one other instance of what I name the cognitive shortcut paradox—AI instruments that make improvement simpler can forestall builders from constructing the very expertise they should use these instruments successfully. Builders who rely solely on MCP to deal with messy knowledge by no means be taught to acknowledge when knowledge structure is problematic, similar to builders who rely solely on instruments like Copilot or Claude Code to generate code by no means be taught to debug what it creates.
The Hidden Prices of Information Hoarding
Groups use MCP as a result of it really works. Many groups fastidiously plan their MCP knowledge structure, and even groups that do fall into the information hoarding entice nonetheless ship profitable merchandise. However MCP remains to be comparatively new, and the hidden prices of information hoarding take time to floor.
Groups typically don’t uncover the issues with a knowledge hoarding method till they should scale their purposes. That bloated context that hardly registered as a value on your first hundred queries begins displaying up as an actual line merchandise in your cloud invoice once you’re dealing with tens of millions of requests. Each pointless area you’re passing to the AI provides up, and also you’re paying for all that redundant knowledge on each single AI name.
Any developer who’s handled tightly coupled courses is aware of that when one thing goes improper—and it at all times does, finally—it’s so much more durable to debug. You typically find yourself coping with shotgun surgical procedure, that basically disagreeable state of affairs the place fixing one small drawback requires modifications that cascade throughout a number of elements of your codebase. Hoarded knowledge creates the identical sort of technical debt in your AI programs: When the AI provides a improper reply, monitoring down which area it used or why it trusted one system over one other is troublesome, typically unimaginable.
There’s additionally a safety dimension to knowledge hoarding that groups typically miss. Every bit of information you expose by means of an MCP instrument is a possible vulnerability. If an attacker finds an unprotected endpoint, they will pull the whole lot that instrument gives. Should you’re hoarding knowledge, that’s your total buyer database as a substitute of simply the three fields truly wanted for the duty. Groups that fall into the information hoarding entice discover themselves violating the precept of least privilege: Purposes ought to have entry to the information they want, however no extra. That may convey an infinite safety threat to their complete group.
In an excessive case of information hoarding infecting a whole firm, you may uncover that each staff in your group is constructing their very own blob. Assist has one model of buyer knowledge, gross sales has one other, product has a 3rd. The identical buyer appears to be like utterly completely different relying on which AI assistant you ask. New groups come alongside, see what seems to be working, and duplicate the sample. Now you’ve received knowledge hoarding as organizational tradition.
Every staff thought they had been being pragmatic, delivery quick, and avoiding pointless arguments about knowledge structure. However the hoarding sample spreads by means of a company the identical method technical debt spreads by means of a codebase. It begins small and manageable. Earlier than you understand it, it’s in all places.
Sensible Instruments for Avoiding the Information Hoarding Lure
It may be actually troublesome to educate a staff away from knowledge hoarding after they’ve by no means skilled the issues it causes. Builders are very sensible—they wish to see proof of issues and aren’t going to take a seat by means of summary discussions about knowledge possession and system boundaries when the whole lot they’ve achieved to date has labored simply nice.
In Studying Agile, Jennifer Greene and I wrote about how groups resist change as a result of they know that what they’re doing at the moment works. To the particular person attempting to get builders to vary, it might appear to be irrational resistance, nevertheless it’s truly fairly rational to push again towards somebody from the skin telling them to throw out what works at the moment for one thing unproven. However similar to builders finally be taught that taking time for refactoring speeds them up in the long term, groups must be taught the identical lesson about deliberate knowledge design of their MCP instruments.
Listed here are some practices that may make these discussions simpler, by beginning with constraints that even skeptical builders can see the worth in:
- Construct instruments round verbs, not nouns. Create
checkEligibility()orgetRecentTickets()as a substitute ofgetCustomer(). Verbs power you to consider particular actions and naturally restrict scope. - Discuss minimizing knowledge wants. Earlier than anybody creates an MCP instrument, have a dialogue about what the smallest piece of information they should present for the AI to do its job is and what experiments they will run to determine what the AI actually wants.
- Break reads other than reasoning. Separate knowledge fetching from decision-making once you design your MCP instruments. A easy
findCustomerId()instrument that returns simply an ID makes use of minimal tokens—and may not even should be an MCP instrument in any respect, if a easy API name will do. ThengetCustomerDetailsForRefund(id)pulls solely the particular fields wanted for that call. This sample retains context centered and makes it apparent when somebody’s attempting to fetch the whole lot. - Dashboard the waste. The very best argument towards knowledge hoarding is displaying the waste. Observe the ratio of tokens fetched versus tokens used and show them in an “data radiator” fashion dashboard that everybody can see. When a instrument pulls 5,000 tokens however the AI solely references 200 in its reply, everybody can see the issue. As soon as builders see they’re paying for tokens they by no means use, they get very fascinated about fixing it.
Fast odor check for knowledge hoarding
- Instrument names are nouns
(getCustomer())as a substitute of verbs(checkEligibility()). - No one’s ever requested, “Do we actually want all these fields?”
- You possibly can’t inform which system owns which piece of information.
- Debugging requires detective work throughout a number of knowledge sources.
- Your staff hardly ever or by no means discusses the information design of MCP instruments earlier than constructing them.
Wanting Ahead
MCP is a straightforward however highly effective instrument with monumental potential for groups. However as a result of it may be a critically necessary pillar of your total software structure, issues you introduce on the MCP stage ripple all through your challenge. Small errors have large penalties down the street.
The very simplicity of MCP encourages knowledge hoarding. It’s a straightforward entice to fall into, even for skilled builders. However what worries me most is that builders studying with these instruments proper now may by no means be taught why knowledge hoarding is an issue, and so they received’t develop the architectural judgment that comes from having to make exhausting decisions about knowledge boundaries. Our job, particularly as leaders and senior engineers, is to assist everybody keep away from the information hoarding entice.
Once you deal with MCP choices with the identical care you give any core interface—maintaining context lean, setting boundaries, revisiting them as you be taught—MCP stays what it must be: a easy, dependable bridge between your AI and the programs that energy it.
