pen.dev MCP
Use pen.dev in the IDE or desktop app and its local pencil MCP server to read and edit .pen files.
pen.dev is a vector design tool available as a desktop app, VS Code / Cursor extension, and CLI. Its designs use .pen files. When the desktop app or IDE extension is running with a document open, external agents can connect to its local MCP server, whose server identifier remains pencil.
That connection describes the local MCP hop only. Model context and provider traffic follow the privacy and data-handling behavior of the external client and model provider you choose.
How MCP works with pen.dev
From pen.dev’s AI integration documentation:
- Install the desktop app or IDE extension and open the
.pendocument the agent should use. - Enable the desired client under Settings (⚙️) → MCP, then start or reload that client.
- Confirm
pencilappears in the client’s MCP server list. - The public server currently exposes
get_style,read_skill,get_app_state, andexecute;browserandspawn_agentsare conditional.
For installation and client-specific steps, use pen.dev MCP (full) in the Model Context Protocol section.
Tools you are likely to see
The installed version is authoritative. Check the client’s live tool list before writing prompts around a specific schema. The former batch_design / batch_get guidance is obsolete; current public tools center on execute plus state, style, and skill helpers.
Exact names and schemas change; verify with /mcp in your client.