Published 24 July 2026 · Source dated 25 November 2024
Anthropic's open Model Context Protocol, launched late 2024, is now the standard plenty of design and dev AI agents plug into. It's gone from new spec to de facto standard fast.
Anthropic open-sourced MCP as a universal way for AI models to connect to external tools and data — one plug instead of every app building its own custom integration. Since then, Figma, Cursor, and a growing catalog of coding and design tools have adopted it as the shared standard.
**Why established, not hype**: it's had 18+ months of real-world use across major tools, not a flash launch. For a junior across Figma and Penpot, you don't need to configure a server yourself — just know what MCP does when a teammate mentions it, because it explains why 'AI agent' features suddenly understand your file's components and styles.
Coach
Skim Anthropic's original MCP announcement, then ask a dev or PM colleague which MCP-connected tools your team already uses.
A hands-on tutorial shows Claude and Cursor using MCP to pull live project context instead of guessing. This is squarely adoption: multiple major AI tools now support the same open protocol Figma uses too.
youtube.com ·
Adoption
MCP is quietly becoming the default for AI dev tools
Cursor's Model Context Protocol integrations have passed ten essential connectors linking AI assistants to databases, APIs and design tools, with more expected across the product lifecycle. It's less flashy than agent demos, but it's the plumbing that makes those demos actually work.
zoer.ai ·
Adoption
MCP servers are now table stakes for AI agents
MCP (Model Context Protocol) has become the standard bridge letting AI agents like Cursor, Claude Code and Figma's own agent pull in real project context. It's no longer a niche integration — it's expected infrastructure across tools.