Vector design / CONNECTION GUIDE Inkscape MCP Servers for Claude Code, Codex & Cursor A community MCP server offers structured SVG inspection, editing and export, with optional control of a running Inkscape instance.
Integration documentation MCP · Live & file workflows
A community MCP server offers structured SVG inspection, editing and export, with optional control of a running Inkscape instance.
Platforms: Linux, macOS, Windows
Claude Code · Documented The maintainer provides a Claude Code setup.
Codex · MCP compatible Uses MCP; agent-specific setup instructions are not included in the linked documentation.
Cursor · MCP compatible Uses MCP; agent-specific setup instructions are not included in the linked documentation.
Requirements and limitations Python 3.12+, uv or pipx, a permitted SVG workspace, and Inkscape 1.4.x on PATH for rendering, export and geometry operations.
Headless-first does not mean every desktop operation is available. Optional live mode and advanced actions have distinct requirements; review the maintainer documentation.
MCP · Headless workflow
An SVG editing server combining file operations with an Inkscape shell and browser preview.
Platforms: Windows, macOS, Linux
Claude Code · Documented The integration documentation explicitly names this client.
Codex · Documented The integration documentation explicitly names this client.
Cursor · Documented The integration documentation explicitly names this client.
Requirements and limitations Inkscape 1.2 or newer, Python 3.11 or newer, and uv.
The server edits SVG files and uses an Inkscape shell; it is not a bridge to the active editor window.
MCP · Live & file workflows
An Inkscape MCP server with both headless operations and a D-Bus live bridge.
Platforms: Windows, Linux
Claude Code · Documented The integration documentation explicitly names this client.
Codex · MCP compatible MCP support suggests compatibility; this client is not documented by the maintainer.
Cursor · MCP compatible MCP support suggests compatibility; this client is not documented by the maintainer.
Requirements and limitations Inkscape and the MCP server; live integration additionally requires D-Bus.
Live control uses D-Bus. On Windows the bridge manages its own Inkscape instance instead of attaching to a manually launched window.
MCP · Live app
A Linux Inkscape extension and MCP bridge for editing open SVG documents.
Platforms: Linux
Claude Code · Documented The integration documentation explicitly names this client.
Codex · Documented The integration documentation explicitly names this client.
Cursor · MCP compatible MCP support suggests compatibility; this client is not documented by the maintainer.
Requirements and limitations Linux, Inkscape, its extension and the documented Python dependencies.
The live bridge is Linux-only and relies on D-Bus.
Compare connections Compare how each route works, what it can do, and what you need to run it.
Connection Workflow and platform Capabilities Documented agents Requirements and limitations Inkscape MCP MCP Live & file workflows Claude Code Python 3.12+, uv or pipx, a permitted SVG workspace, and Inkscape 1.4.x on PATH for rendering, export and geometry operations. Inkscape MCP · jaags-dev MCP Headless workflow Claude Code, Codex, Cursor Inkscape 1.2 or newer, Python 3.11 or newer, and uv. Inkscape MCP · aravindev MCP Live & file workflows Claude Code Inkscape and the MCP server; live integration additionally requires D-Bus. Inkscape MCP · inkmcp MCP Live app Claude Code, Codex Linux, Inkscape, its extension and the documented Python dependencies.
How it works
Capabilities
Documented agents
Requirements and limitations Python 3.12+, uv or pipx, a permitted SVG workspace, and Inkscape 1.4.x on PATH for rendering, export and geometry operations.
Headless-first does not mean every desktop operation is available. Optional live mode and advanced actions have distinct requirements; review the maintainer documentation.
How it works
Capabilities
Documented agents
Requirements and limitations Inkscape 1.2 or newer, Python 3.11 or newer, and uv.
The server edits SVG files and uses an Inkscape shell; it is not a bridge to the active editor window.
How it works
Capabilities
Documented agents
Requirements and limitations Inkscape and the MCP server; live integration additionally requires D-Bus.
Live control uses D-Bus. On Windows the bridge manages its own Inkscape instance instead of attaching to a manually launched window.
How it works
Capabilities
Documented agents
Requirements and limitations Linux, Inkscape, its extension and the documented Python dependencies.
The live bridge is Linux-only and relies on D-Bus.
Questions before setup Does one integration cover every workflow? No such claim is made. Check the capability list, requirements and limitations of each route, then test a copy of a representative project.