Put MCP Next to Your API, Not on Top: Stacked vs Side-by-Side Architectures Compared
rseroter · x · 2026-11-18
rseroter shares an article arguing MCP should sit beside your API rather than stacked on top of it, with a diagram contrasting the two patterns.
- Stacked: MCP server layered over the API server — one extra hop and two contracts to maintain
- Side by side: MCP and REST coexist, with an aggregate/consume engine serving both agents and apps from upstream systems
He asks whether teams actually deploy MCP this way or mostly stack it on existing public APIs.
More from coding & agent
- Agent memory benchmarks measure recall, but provenance is what bites in production — Mr_Daud_9899 · 2026-11-18
- 12 frontier models in a fake company Slack: most pitched in uninvited—5 rules that fixed it — AIFlow_ML · 2026-11-18
- Replit launches Missions, an agent-swarm harness that hits your goals within a set budget — amasad · 2026-11-18
- YC Paper Club: why the harness matters more than the model — eherrerosj · 2026-11-18
- AI-built Paris replica streams city blocks in real time with historically accurate traffic — Dimillian · 2026-11-18
- Reflection launches Trusted Access Program, starting with autonomous pentest tool Laser — brandondamos · 2026-11-18