Creativity · MCP — server

MCP Sketch Server

The MCP Sketch Server reads local .sketch files using the Sketch File Format and talks to Sketch Cloud for shared libraries. It exposes symbols, layer trees, text styles, color variables, and exported assets as tools — letting an LLM generate design-system docs, React component stubs, or accessibility reports.

MCP facts

Kind: server
Ecosystem: anthropic-mcp
Language: TypeScript (Node)
Transports: stdio

Capabilities

Tools: list_symbols, get_layer, extract_color_variables, export_slice
Resources: sketch://file/{path}/symbol/{id}
Auth: Sketch Cloud personal access token for Cloud libraries

Install

npx -y @community/mcp-server-sketch

Configuration

{
  "mcpServers": {
    "sketch": {
      "command": "npx",
      "args": ["-y", "@community/mcp-server-sketch", "/Users/you/Designs"],
      "env": {
        "SKETCH_CLOUD_TOKEN": "${SKETCH_CLOUD_TOKEN}"
      }
    }
  }
}

Frequently asked questions

Does it require the Sketch macOS app?

For local .sketch parsing, no — it uses the documented file format. Only Sketch Cloud library interactions require network access; they do not require the desktop app.

Can it modify designs?

Write support is limited. Generating new Sketch files programmatically is possible using the Sketch File Format, but most MCP implementations focus on read paths.

Where does Sketch fit today?

Sketch remains popular among Mac-focused teams and agencies. Many enterprise design systems still live in Sketch libraries, which is why the MCP server stays valuable.

Sources

Sketch Developer documentation — accessed 2026-04-20
Model Context Protocol — accessed 2026-04-20
MCP servers repo — accessed 2026-04-20