{"by":"simonw","id":49779718,"kids":[49782293,49786023,49785637,49779780,49779878,49783636,49787207,49787673,49786383,49789376,49788767,49782200,49789092,49787215,49792302,49789001,49780697,49785746,49782621,49791687,49779763,49786493,49799745,49787700,49783308,49783293,49808905,49799480,49799950,49782130],"parent":49779329,"text":"This article entirely misses the value that MCP brings today.

Sure, there's almost no reason to use MCPs if you are running a full-blown terminal agent (Claude Code, Codex, Meta Muse, OpenClaw etc) with unfettered internet access - just let it call APIs directly.

If you want to operate something that's less YOLO than that, you'll find yourself wanting:

1. Control over exactly which external services it can access

2. A way to handle authentication that doesn't allow the agent to directly access API keys

3. A sensible UI to allow users to connect and authenticate further services

4. Strong audit logging for what's going on

MCP makes all of that so much easier to provide.

Thinking MCP is obsolete because full coding agents don't need it misses out on all of the other things we might want to build.","time":1789935881,"type":"comment"}