A server for processing Sketch files and generating code using MCP tools.
This Sketch MCP server has 17 tools with complete JSON Schema definitions and descriptions. However, quality varies: most tools are well-named with verb prefixes (get_, list_, find_), but many descriptions are terse (10-50 chars) and lack guidance on WHEN to use each tool over similar alternatives. Parameter descriptions are present but often minimal. Output schemas are largely undocumented, the source shows function signatures but not response field documentation. Error handling is basic: no recovery guidance, no error classification. The tool composition is sound (single responsibility per tool, good chaining via IDs), but several tools expose implementation details (e.g., renderNodeAsBase64 with format enum) rather than user-intent names. No security issues detected (read-only risk category confirms no destructive operations), but descriptions should clarify prerequisites and expected input types more explicitly.
Find nodes by name pattern
Get complete document structure with all pages and their hierarchies
Get detailed information for multiple nodes by their IDs in a single call
Get detailed information about a node by its ID
Get the position of a node by its ID
Get summary of nodes with statistics and grouping to reduce token usage
Get complete hierarchical structure of a page with all node information
Tool descriptions are inconsistently brief (10-65 chars) and lack WHEN-to-use guidance. Similar tools (getNodeInfo vs getMultipleNodeInfo, listPages vs getDocumentStructure) have no distinguishing context to guide LLM selection.
Output schemas are undocumented in source code. Tool descriptions do not specify what fields are returned, their types, or whether pagination/limits apply. LLMs cannot reason about downstream tool dependencies (e.g., what IDs to extract from listNodes response).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 62 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 46 | 2024-11-05+ | v1 |
Get styles from Symbol Instance including overrides applied to Symbol Master
Get all Symbol Instances in the Sketch document
Get Symbol Master by its Symbol ID
Get all Symbol Masters in the Sketch document
List nodes with optional filtering
List nodes within a specific page
List all pages in the Sketch document
Load a Sketch configuration object
Load a Sketch file from a file path
Render a node as Base64 encoded image (SVG format) for AI to visualize the actual appearance
No error handling documentation. Tools do not specify what happens on invalid nodeId, missing pageId, or malformed path. Descriptions lack recovery guidance (e.g., 'If node not found, try findNodesByName() with partial name').
Parameter descriptions lack format/constraint details. nodeId, pageId, and symbolID parameters are described only as 'The X' with no guidance on format, length, or valid range. LLMs may pass invalid values.
loadSketchByPath and loadSketchByConfig descriptions do not clarify that they LOAD/SWITCH the active Sketch document (state-changing behavior). This violates the tool-description pattern and may cause LLMs to misunderstand side effects.
getDocumentStructure has redundant/overlapping parameters (includeDetails + fields/excludeFields; summaryMode + groupSimilar). Description does not explain interaction or which combinations are recommended.
renderNodeAsBase64 exposes implementation detail (format enum: svg, png) rather than user-intent naming. Consider renaming to describe the purpose (visualize_node, export_node_image) or clarifying why format choice matters.