Building a tool to turn existing API collections into MCP servers — how thick should the tool layer be?
agentrsdg · reddit · 2026-09-08
A developer is building a tool that generates MCP servers from existing API collections, letting agents work through a cleaner, more controlled interface while APIs stay as the underlying system.
Key design questions raised:
- Is converting endpoints into tools enough, or should the MCP layer include predefined, grouped, or chained actions as a middle layer?
- How to balance deterministic MCP interfaces vs. agent autonomy?
- What would a generic conversion process look like when each MCP server is custom?
The post seeks community input on MCP granularity design — a real engineering tradeoff in agent tooling.
More from coding & agent
- Xiaomi launches invite-only beta of MiMo Desktop, an agent that ships finished work — teortaxesTex · 2026-09-08
- Coval Raises $28M, Launches First Self-Improving Voice Agents With Phonely's Alma Model — massimosgrelli · 2026-09-08
- EU compliance checks as prepaid MCP tools for agents, from €0.10 per call — jithox_AI · 2026-09-08
- Same prompt, four models, one motorcycle: Blender MCP comparison crowns Astra — a10ondr · 2026-09-08
- Dev wires pre-push hook to run tests, SSH-sign a receipt as a git note — fforres · 2026-09-08
- 21 days to OpenAI DevDay: Codex team tracking multiple launches in 28-page deck — reach_vb · 2026-09-08