今日已更新 80 条资讯 | 累计 20052 条内容
关于我们

MCP vs Direct API Calls — My Agent Stack Has Zero MCP Servers

Ted 2026年06月10日 11:32 4 次阅读 来源:Dev.to

The Model Context Protocol is everywhere right now. Every agent tutorial opens with "first, set up your MCP servers." And yet the agent stack running on the machine I'm typing this from — search monitoring, Telegram alerting, social posting, a voice assistant — contains exactly zero MCP servers. Everything talks to external services through direct API calls. That's not a rejection of MCP. It's a protocol, not a movement — and the flood of agent-architecture content keeps turning plumbing decisions into identity decisions. You're not an "MCP shop" or "behind." You're making a per-workload integration choice, and it comes down to two gates: one decides whether MCP is even the relevant category, the other decides whether it's worth the overhead. Gate one — relevance: does a model pick the tool at runtime? MCP exists to solve a specific problem: a language model, mid-session, deciding which tool to use. The protocol standardises how a model discovers tools, what their schemas look like, and how results come back. That's its entire reason to exist — it's a model-facing protocol. If no model is ever choosing, MCP isn't the relevant category; you'd share a library or stand up a plain service. Now look at what most automation actually is. My morning report pipeline: Cron fires at 8:30 Script calls the Google Search Console API Script formats the numbers Script posts to Telegram The model isn't deciding anything here. There's no runtime tool choice — the model's only job in pipelines like this is reading the data at one step, not fetching it. The call order is fixed, every day, forever. For this workload, MCP isn't the question. One subtlety that matters later: gate one is evaluated over a tool surface's consumers , not over the workload in front of you. The cron pipeline will never pass it. But the search-data access underneath it might — the day a model-driven client wants the same data. The pipeline isn't an MCP candidate; the surface can become one. Either way: being an

本文内容来源于互联网,版权归原作者所有
查看原文