Design-to-code and beyond: inside Coinbase’s MCP ecosystem
summary
Coinbase runs a cross platform design system CDS with 100+ components and eight major releases, and solves slow handoffs by exposing Code Connect snippets in Figma plus per component context served on demand via MCP so LLMs fetch only needed props and import paths. A SourceCraft MCP indexes repos to measure adoption and plan deprecations. An internal MCP app store spawns 100+ MCPs used ~1,000,000 times cutting token use and speeding dev workflows.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:32CDS overview
- 3:25Design-to-code challenges
- 4:31AI tools limitations
- 5:53Model Context Protocol MCP
- 6:37CDS MCP server
- 7:41Figma MCP integration
- 8:03Measuring MCP adoption
- 9:08MCP app store
- 10:12MCP ecosystem impact
- 10:54Key takeaways and conclusion
related talks
31mDesign to Code in 2026: Context-First Development with Figma MCP
22mHow Block Operationalized MCP At Scale
15mFull Spec MCP: Hidden Capabilities of the MCP spec
27mHow We Built Our First MCP Server: Lessons From the Trenches at Hud
16mBuilding Interactive UIs in VS Code with MCP Apps
17mMCP Is Not Good Yet
25mCruising the AI Highway: Standardized MCP Deployment and Governance With Backstage
20mConnecting code with craft
