From Maharshi Patel · · 40s
Why MCP Was Always a Bad Idea
MCP protocol outdated as AI agents now handle APIs directly.
In brief
MCP protocol outdated as AI agents now handle APIs directly. AI agents can now access APIs without MCP servers, ending the protocol's relevance. Originally reported by Maharshi Patel.
Quick answers
- What now?
- Delete mcp servers; use http apis directly.
- What is the key takeaway from Why MCP Was Always a Bad Idea?
- AI agents can now access APIs without MCP servers, ending the protocol's relevance.
MCP's origins
MCP started in 2024 for simple agent tool access.
“MCP was released in november 2024 by the anthropic team”
Early MCP growth
Users quickly adopted MCP for productivity gains.
“We saw an explosion in mcp adoption”
MCP's context bloat
Too many tools overloaded agent memory.
“Each server would come with multiple tools, each with its own schema”
Model improvements
Agents now write scripts and call APIs directly.
“The models got better. They are now able to execute code on a computer”
Cloudflare's Code Mode
Cloudflare offers better mcp alternatives with scripts.
“Cloudflare even launched code mode, a better way to use mcp”
CLIs replace mcp
Agents use, help to discover services without mcp.
“The llms have figured out how to use the, help command to discover clis”
What now?
Delete mcp servers; use http apis directly.
“We delete most of our mcp servers. That’s it.”
In short
AI agents can now access APIs without MCP servers, ending the protocol's relevance.
