How Block Operationalized MCP At Scale
summary
Claims rapid rollout: Block scales MCP across a 12,000 person company in two months and achieves measurable gains. Engineers using Goose save about 8–10 hours a week for 75% of users, adoption doubles then weekly engagement rises 50%, and the repo hits GitHub trending number one. Built an extensible MCP client, desktop and CLI apps, SSO OAuth servers, dynamic context management, summaries, recipes and a deploy MCP, and now bundles 100+ internal MCP servers so nonengineers actually use it securely.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:02Adopting MCP standard
- 4:10Expanding Goose to all teams
- 6:04Design choices enabling adoption
- 8:19Overcoming installation barriers
- 9:26Internal MCP servers
- 11:14Non-engineer MCP creators
- 11:55Context window challenges
- 13:33Authentication for users
- 14:48Slack communities and education
- 17:09Real-world use cases
- 19:28Reusable workflows
- 20:33AI process navigation
- 21:40Scaling MCP inclusively
related talks
17mMCP Is Not Good Yet
12mDesign-to-code and beyond: inside Coinbase’s MCP ecosystem
25mCruising the AI Highway: Standardized MCP Deployment and Governance With Backstage
27mHow We Built Our First MCP Server: Lessons From the Trenches at Hud
55mYour MCP Server is Bad (and you should feel bad)
33mBuild Reasonable Software
28mBuilding MCP servers with VS Code — Level up your MCP
20mBuilding Protected MCP Servers