MCP vs Direct API Calls — My Agent Stack Has Zero MCP Servers
In a post on DEV Community, a developer pushes back against the trend of defaulting to MCP (Model Context Protocol) in agent architectures. The author states that their production agent stack—which includes search monitoring, Telegram alerting, social posting, and a voice assistant—contains zero MCP servers, relying entirely on direct API calls to external services. They argue that MCP is a protocol designed for a specific use case: enabling a language model to discover and select tools dynamically during a session. When no model is making such choices, MCP adds unnecessary overhead. The author suggests that most automation tasks are better served by sharing a library or standing up a plain service, rather than adopting MCP. The post emphasizes that the choice between MCP and direct API calls is a per-workload integration decision, not an identity statement about being an 'MCP shop.'
Challenges the default adoption of MCP, urging developers to evaluate whether their use case actually requires it.