MCP vs API vs CLI: build both on one operations layer, prioritize MCP
hottown · reddit · 2026-11-06
A Wasp guide on which interface to expose to AI agents. Key points: MCP shines in agent-native contexts because it guides agents on both server and client (Claude Code, ChatGPT desktop) and suits human-in-the-loop tasks; APIs and CLIs focus on what agents can do. Advice: build a high-quality MCP server and REST API on one shared operations layer of plain functions with thin adapters; invest most in MCP since it's the agent-first standard; keep APIs for standalone code like nightly syncs, bulk writes, and rerunnable agent scripts (many clients lack MCP code mode); a CLI is rarely necessary unless agents need local file access.
Related event: Wasp Compares MCP vs API vs CLI for AI Agent Integration(4 posts)→
More from coding & agent
- Slack agent Biscuit iterates a party-poll app live, even shipping lazy requests — blixt · 2026-11-06
- Using GrokBot as a 24/7 collector that turns Notion into a live idea database — huangyun_122 · 2026-11-06
- Custom GPTs die Dec 11: if you use someone else's GPT, you can't migrate it — Ok_Negotiation_2587 · 2026-11-06
- ~780 AI slop accounts identified on X; users deploy agents to auto-block them daily — TheZachMueller · 2026-11-06
- Dev runs agentic PR reviews in worktrees, agrees with the agent ~70% of the time — tomaarsen · 2026-11-06
- Formal proofs of tens of millions of lines of code are now feasible, says Anthropic engineer — morqon · 2026-11-06