The customer
A Series B developer tools platform with ~32,000 active accounts. Their product surface is wide — projects, PRs, issues, deploys — and customers had started asking for an MCP integration so they could pipe the platform into Claude, Cursor, and internal agents.
What they tried first
An internal "20% time" project. Two engineers, three months, no shipped server. The MCP spec moved twice during that window and the in-house attempt fell behind each time.
The task they submitted
Ship an MCP server that exposes our top 40 product surfaces as tools, with OAuth-style auth and audit logging. Must run inside our existing Go monolith.
Our approach
Tuesday: schema-first design — extracted 47 tools from the public REST API, generated a typed MCP server stub in Go. Wednesday: auth flow piggy-backed on the existing PAT system; per-tool scopes; audit log table. Thursday: 47 tool tests in CI plus a soak test that runs the server through a 1,000-request loop. Friday: load-tested at 4× their projected peak, deployed behind a feature flag.
The outcome
Public launch the following Tuesday. By day 60: 22% week-over-week growth in WAU among the segment that adopted the MCP, and zero P0 incidents traced to the server. The PM team is now staffing a dedicated "agent integrations" pod.
“Two engineers tried this in spare cycles for 3 months. Boundev did it in a week — and shipped it better.”