How GitHub, Stripe and Cloudflare design MCP servers: two tools, big context gap
ostwal · reddit · 2026-11-18
Analyzing public docs of GitHub, Stripe, Notion, Atlassian and Cloudflare MCP servers: most are thin wrappers over existing APIs. Stripe exposes four generic tools (search/details/read/write); Cloudflare covers 2,500+ endpoints with just search() and execute(). GitHub's one-tool-per-endpoint approach with 100 tools made agents worse. Generic tools solve tool count but not context — descriptions don't explain entity IDs, lookup order, or domain meaning. Context lives in server instructions, search→fetch→act flows, tool grouping, and return shapes; instructions are hints, not contracts. The author found no production server using MCP resources/prompts for context.
More from coding & agent
- philschmid: replace built-in multi-agent features with an MCP server of the harness itself — _philschmid · 2026-11-18
- Full prompt released: one-shot 15s Pixar-style 3D peacock video, covers walking, fanning and rain — CodeByPoonam · 2026-11-18
- WorkBuddy AI office test: clean, consistent 10-slide onboarding deck from a single prompt — CodeByPoonam · 2026-11-18
- The killer app of agentic programming is building harnesses for agentic programming — danbri · 2026-11-18
- Dev shows agentic video editing with HyperFrames + Claude, ditching FFmpeg pain — toolstelegraph · 2026-11-18
- ETH's AuXSpec: executable postconditions as RL reward, 27B model beats frontier LLMs at SpecGen — eth-algopt · 2026-11-18