Design stacks embrace MCP

Model Context Protocol is turning design software into something an artificial intelligence client can browse and edit through a standard connector, and Sketch is the latest design vendor to lean into it. (modelcontextprotocol.io) (sketch.com) Sketch said last week that its new Model Context Protocol server lets “any MCP-compatible AI client” connect to Sketch, including Claude Code, Claude Desktop, Visual Studio Code, Cursor, Codex and Antigravity. Sketch’s documentation says the feature runs through a local server inside the Mac app. (sketch.com 1) (sketch.com 2) The company said the server is local-only, cannot be accessed remotely, and does not require customers to buy tokens, an extra tier or an add-on. Sketch also says the server is off by default and users control when outside clients connect. (sketch.com) (forum.sketch.com) Model Context Protocol, or MCP, is an open standard Anthropic introduced on November 25, 2024 for connecting large language model applications to outside tools and data sources. The protocol’s published specification describes it as a standardized way for artificial intelligence apps to request context and take actions across software systems. (anthropic.com) (modelcontextprotocol.io) That standard is now showing up in design workflows that used to be split across screenshots, copy-and-paste handoffs and manual rebuilds. Figma said last month that its Claude Code to Figma workflow turns captured screens from production code into editable Figma frames that teams can annotate, duplicate and refine. (figma.com) Anthropic’s Figma plugin listing says the integration connects Claude Code directly to Figma files so users can extract component information, read design tokens and translate designs into code. The listing showed 88,279 installs when it was crawled yesterday. (claude.com) Figma’s own explainer says MCP works as a two-way protocol: software vendors expose an MCP server, and artificial intelligence tools use that server to access data or take actions inside the product. In plain terms, that means a design app can expose layers, components or tokens through one common interface instead of building a separate integration for each assistant. (figma.com) (modelcontextprotocol.io) Sketch is pitching that same pattern to designers who want an assistant to inspect documents, swap components or make repetitive changes without leaving the canvas. Its marketing page says users can connect ChatGPT and Claude to Sketch designs through the MCP server, while the documentation frames the server as a bridge to outside clients rather than a standalone chatbot inside Sketch. (sketch.com 1) (sketch.com 2) The shift is less about one model or one design app than about a common pipe between them. As more design tools publish MCP servers and more coding assistants add MCP support, the stack designers describe is starting to look less like a bundle of one-off plugins and more like interoperable infrastructure. (modelcontextprotocol.io) (github.com)