Sketch MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_codeB | Run ECMAScript 2020 Sketch plugin scripts. (This is a placeholder tool description provided while the Sketch MCP server is not available. Try to re-fetch the tool list after the user has started Sketch and enabled the MCP Server) |
| get_selection_as_imageA | Returns a visual representation of currently selected Sketch layers as a PNG image. (This is a placeholder tool description provided while the Sketch MCP server is not available. Try to re-fetch the tool list after the user has started Sketch and enabled the MCP Server) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely different purposes: one captures a visual representation of selected layers, the other executes arbitrary scripts. There is no overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern using snake_case: get_selection_as_image and run_code. The naming is clear and predictable.
With only 2 tools, the server feels underpowered for a design tool like Sketch. Typical MCP servers have at least a handful of tools covering core operations.
The server lacks obvious operations for a Sketch MCP (e.g., creating layers, modifying documents, exporting). The run_code tool acts as a catch-all, but the surface is incomplete for structured workflows.