Skip to content
Back to search

inkscape_mcp

MCP server that lets AI agents drive Inkscape — interactively alongside the GUI or headlessly from the CLI

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/aravindev/inkscape_mcp with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/aravindev/inkscape_mcp'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/aravindev--inkscape-mcp/badge.svg)](/listings/aravindev--inkscape-mcp)

HTML

<a href="/listings/aravindev--inkscape-mcp"><img src="/api/listings/aravindev--inkscape-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

> Tested with **Inkscape 1.4.4** on Ubuntu 24.04.

# 1. Install Inkscape + system headers for pycairo / pygobject
sudo add-apt-repository ppa:inkscape.dev/stable
sudo apt update
sudo apt install inkscape libcairo2-dev libgirepository-2.0-dev libgirepository1.0-dev \
pkg-config python3-dev xclip
# xclip stages SVG fragments for clipboard-based insert into the canvas.
# Clipboard ops auto-detect the backend. On Wayland (the Ubuntu 24.04 default)
# wl-clipboard is preferred if installed; otherwise xclip is used, which works
# because Inkscape runs as an XWayland client. Either package is sufficient.

# 2. Register with Claude Code (uvx fetches inkscape-mcp from PyPI on first run)
claude mcp add inkscape_mcp -s user -- uvx inkscape_mcp
claude mcp list | grep inkscape_mcp   # → ✓ Connected

# 3. (Re)start Inkscape so it picks up the bundled extensions
# The MCP server auto-installs its inkex extensions to
# ~/.config/inkscape/extensions/inkscape_mcp/ on first boot. Inkscape only
# scans the extensions dir at startup, so close + reopen Inkscape once.
# Verify via:
#   inkscape_system(operation="diagnostics")  → bridge.needs_restart should be false

That's it. Ask the agent to convert an SVG, query an object's bounding box, run a boolean union — it'll pick the right tool.

Alternative install paths

# Plain pip into a venv
pip install inkscape-mcp

# uv into a project
uv add inkscape-mcp

The PyPI name is `inkscape-mcp` (hyphen). The Python import name is `inkscape_mcp` (underscore — PEP 8 / valid identifier). Both `pip install inkscape-mcp` and `pip install inkscape_mcp` resolve to the same project (PEP 503 name normalization).

Windows

The headless tools install and run exactly as above. The **live** bridge (`inkscape_live`) needs one extra piece: a Windows `dbus-daemon`, which isn't part of a stock Windows install. The simplest source is [MSYS2](https://www.msys2.org/) — install it, then:

pacman -S mingw-w64-x86_64-dbus   # provides dbus-daemon.exe; MCP auto-discovers it

`gdbus.exe` itself already ships with Inkscape, and the daemon's dependency DLLs are covered by Inkscape's, so MSYS2 is only the delivery vehicle for that one `dbus-daemon.exe`. If you already have one elsewhere, point `INKSCAPE_MCP_DBUS_DAEMON` at it (and `INKSCAPE_MCP_GDBUS` if `gdbus.exe` isn't found automatically).

On Windows the live bridge **launches and manages its own Inkscape instance** — a hand-launched Inkscape isn't on the bus, so have the agent `open_file` a document to work on it. Tested on Inkscape 1.4.x.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 194 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # Inkscape MCP
  2. <p align="center">
  3. <img src="https://raw.githubusercontent.com/aravindev/inkscape_mcp/main/assets/social-preview.png" alt="inkscape-mcp — drive Inkscape from an AI agent" width="100%">
  4. </p>
  5. Let your AI agent design, edit, and analyze vector graphics through Inkscape — live alongside a running Inkscape window, or headless from the command line.
  6. <p>
  7. <a href="https://pypi.org/project/inkscape-mcp/"><img src="https://img.shields.io/pypi/v/inkscape-mcp.svg?style=flat-square&logo=pypi&logoColor=white&label=PyPI" alt="PyPI"></a>
  8. <a href="https://pypi.org/project/inkscape-mcp/"><img src="https://img.shields.io/badge/Python-3.14-3776AB?style=flat-square&logo=python&logoColor=white" alt="Python 3.14"></a>
  9. <a href="https://pypi.org/project/inkscape-mcp/"><img src="https://img.shields.io/pypi/dm/inkscape-mcp.svg?style=flat-square&label=downloads" alt="PyPI downloads"></a>
  10. <a href="https://github.com/aravindev/inkscape_mcp/actions/workflows/ci.yml"><img src="https://img.shields.io/github/actions/workflow/status/aravindev/inkscape_mcp/ci.yml?branch=main&style=flat-square&logo=github&label=CI" alt="CI"></a>
  11. <a href="https://github.com/aravindev/inkscape_mcp/blob/main/LICENSE"><img src="https://img.shields.io/github/license/aravindev/inkscape_mcp?style=flat-square&color=yellow" alt="License"></a>
  12. </p>
  13. <p>
  14. <a href="https://modelcontextprotocol.io"><img src="https://img.shields.io/badge/MCP-2.x-1F6FEB?style=flat-square&logo=anthropic&logoColor=white" alt="MCP"></a>
  15. <a href="https://github.com/PrefectHQ/fastmcp"><img src="https://img.shields.io/badge/FastMCP-4.1-7c5cfc?style=flat-square" alt="FastMCP"></a>
  16. <a href="https://inkscape.org"><img src="https://img.shields.io/badge/Inkscape-1.4.4-000000?style=flat-square&logo=inkscape&logoColor=white" alt="Inkscape"></a>
  17. <a href="#getting-started"><img src="https://img.shields.io/badge/platform-Linux%20%7C%20Windows%20%7C%20macOS-informational?style=flat-square" alt="Platform: Linux | Windows | macOS"></a>
  18. <a href="https://github.com/astral-sh/ruff"><img src="https://img.shields.io/badge/style-ruff-D7FF64?style=flat-square&logo=ruff&logoColor=black" alt="Ruff"></a>
  19. <a href="https://github.com/pre-commit/pre-commit"><img src="https://img.shields.io/badge/pre--commit-enabled-success?style=flat-square&logo=pre-commit&logoColor=white" alt="pre-commit"></a>
  20. </p>
  21. With Inkscape MCP, your coding agent can do everything a designer does in Inkscape — sketch and reshape paths, apply effects and filters, render LaTeX equations, generate barcodes and QR codes, convert between formats, query and rewrite document structure — through plain conversation instead of menu clicks.
  22. Pair it with a **running Inkscape window** and the agent works alongside you — it sees what you have selected, opens property dialogs on your behalf, applies edits that appear on the canvas in real time (each one a normal undo entry you can roll back), and rasterizes its own work to inspect and refine the result. Or run it **headlessly** to batch-convert artwork, automate exports, and build pipelines around vector assets — no GUI required. The full Inkscape feature surface, including its hundreds of bundled extensions, is reachable as tool calls.
  23. ## How it works
  24. 1. The agent calls one of eight portmanteau tools — `inkscape_file`, `inkscape_vector`, `inkscape_analysis`, `inkscape_system`, `inkscape_extension`, `inkscape_gradient`, `inkscape_metadata`, or `inkscape_live` — with an `operation` string that picks the actual behavior.
  25. 2. For headless work the server dispatches through `InkscapeCliWrapper`, which builds and runs an `inkscape --actions=...` (or `--export-...`) command. For live-canvas work it talks to a running Inkscape window over D-Bus and inserts SVG fragments through the XML-edit extension.
  26. 3. Inkscape reads your input file (or the open document), runs the operation, and writes the output.
  27. 4. The server returns dimensions, file paths, validation results, or whatever the operation produces — typed and trimmed for the agent's context window.
  28. No external network. Just the Inkscape binary, an optional running Inkscape window, and your local files.
  29. ## Getting started
  30. > Tested with **Inkscape 1.4.4** on Ubuntu 24.04, Windows 11, and macOS (Apple Silicon).
  31. ```bash
  32. # 1. Install Inkscape + system headers for pycairo / pygobject
  33. sudo add-apt-repository ppa:inkscape.dev/stable
  34. sudo apt update
  35. sudo apt install inkscape libcairo2-dev libgirepository-2.0-dev libgirepository1.0-dev \
  36. pkg-config python3-dev
  37. # 2. Register with Claude Code (uvx fetches inkscape-mcp from PyPI on first run)
  38. claude mcp add inkscape_mcp -s user -- uvx inkscape_mcp
  39. claude mcp list | grep inkscape_mcp # → ✓ Connected
  40. # 3. (Re)start Inkscape so it picks up the bundled extensions
  41. # The MCP server auto-installs its inkex extensions to
  42. # ~/.config/inkscape/extensions/inkscape_mcp/ on first boot. Inkscape only
  43. # scans the extensions dir at startup, so close + reopen Inkscape once.
  44. # Verify via:
  45. # inkscape_system(operation="diagnostics") → bridge.needs_restart should be false
  46. ```
  47. That's it. Ask the agent to convert an SVG, query an object's bounding box, run a boolean union — it'll pick the right tool.
  48. ### Alternative install paths
  49. ```bash
  50. # Plain pip into a venv
  51. pip install inkscape-mcp
  52. # uv into a project
  53. uv add inkscape-mcp
  54. ```
  55. The PyPI name is `inkscape-mcp` (hyphen). The Python import name is `inkscape_mcp` (underscore — PEP 8 / valid identifier). Both `pip install inkscape-mcp` and `pip install inkscape_mcp` resolve to the same project (PEP 503 name normalization).
  56. ### Windows
  57. The headless tools install and run exactly as above. The **live** bridge (`inkscape_live`) needs one extra piece: a Windows `dbus-daemon`, which isn't part of a stock Windows install. The simplest source is [MSYS2](https://www.msys2.org/) — install it, then:
  58. ```sh
  59. pacman -S mingw-w64-x86_64-dbus # provides dbus-daemon.exe; MCP auto-discovers it
  60. ```
  61. `gdbus.exe` itself already ships with Inkscape, and the daemon's dependency DLLs are covered by Inkscape's, so MSYS2 is only the delivery vehicle for that one `dbus-daemon.exe`. If you already have one elsewhere, point `INKSCAPE_MCP_DBUS_DAEMON` at it (and `INKSCAPE_MCP_GDBUS` if `gdbus.exe` isn't found automatically).
  62. On Windows the live bridge **launches and manages its own Inkscape instance** — a hand-launched Inkscape isn't on the bus, so have the agent `open_file` a document to work on it. Tested on Inkscape 1.4.x.
  63. ### macOS
  64. ```bash
  65. # Inkscape 1.4.x from inkscape.org in /Applications, then:
  66. brew install dbus glib uv
  67. git clone https://github.com/aravindev/inkscape_mcp.git
  68. cd inkscape_mcp
  69. uv sync
  70. claude mcp add inkscape_mcp -s user -- uv run --directory "$PWD" inkscape_mcp
  71. ```
  72. The live bridge launches and manages its own Inkscape; use `open_file` to work on a
  73. document. See [docs/INSTALL.md](docs/INSTALL.md#macos).
  74. ## Configuration
  75. The Claude Code entry the install command above creates looks like:
  76. ```json
  77. {
  78. "mcpServers": {
  79. "inkscape_mcp": {
  80. "command": "uvx",
  81. "args": ["inkscape_mcp"]
  82. }
  83. }
  84. }
  85. ```
  86. Pin a non-default Inkscape with `INKSCAPE_BIN=/path/to/inkscape` in the server env; the server only falls back to searching `$PATH` when nothing pins it. Inspect from the agent via `inkscape_system(operation="diagnostics")` — its `config_sources` block reports each tracked setting's effective value alongside where it came from (`env_var`, `config_file`, `cli_flag`, `auto_detected` or `default`).
  87. ## Try asking your agent to…
  88. **Editing the file you have open**
  89. - "Recolor everything blue to red"
  90. - "Open document properties — I can't find the DPI setting"
  91. - "Select the pen tool so I can draw a curve"
  92. - "Show me the XML editor"
  93. - "Hide the snap controls bar"
  94. - "Add a drop shadow to all the rectangles"
  95. - "Convert this monogram to a single compound path"
  96. - "Run a boolean union on the two selected shapes"
  97. **Generating SVG content**
  98. - "Drop in an isometric grid into this document"
  99. - "Generate a calendar for the current month and paste it here"
  100. - "Make me a 24×24 settings cog icon — currentColor stroke, round caps"
  101. **Inspection & format conversion**
  102. - "Export this to a 4× PNG and a print-ready PDF"
  103. - "What's the bounding box of #logo-mark?"
  104. - "Optimize this SVG — strip Inkscape namespace cruft"
  105. - "List every object in the file with its type and size"
  106. **Live-canvas workflows** (Inkscape running)
  107. - "Read what I have selected"
  108. - "Align these three icons horizontally with equal spacing"
  109. - "Swap the whole palette to a warmer earth-tone scheme"
  110. - "Add a 3-stop gradient to the rect with id `hero`"
  111. The agent picks the right tool. It can drive over 1,000 of Inkscape's actions over D-Bus (1,083 app-scope, 163 window-scope and 30 document-only actions such as undo on Inkscape 1.4.4 — ask for the exact figure with `inkscape_live(operation="ping")`), fall back to headless CLI when the GUI isn't running, and run inkex extensions for things D-Bus doesn't cover.
  112. ## Available tools
  113. - **`inkscape_file`** — load, save, convert (PDF/PNG/EPS/PS/…), validate, batch convert.
  114. - **`inkscape_vector`** — 49 ops covering boolean, tracing, path simplification, optimization, alignment, layer export, geometry mutation, barcodes, LPE chains, tile clones.
  115. - **`inkscape_analysis`** — quality scoring, statistics, object lists, layer structure.
  116. - **`inkscape_system`** — server status, diagnostics, extension discovery and execution.
  117. - **`inkscape_extension`** — discover and invoke any installed inkex extension (headless or on the live canvas).
  118. - **`inkscape_gradient`** — gradient-stop manipulation; linear↔radial conversion.
  119. - **`inkscape_metadata`** — read/write Dublin-Core RDF metadata.
  120. - **`inkscape_live`** — drive the running GUI over D-Bus: any Inkscape action (including undo/redo), XML edits, `rasterize` so the agent can see the canvas (preserves undo).
  121. Full operation list in [`docs/TOOLS.md`](docs/TOOLS.md).
  122. ## How the agent learns to use it
  123. An agent that just installed this server doesn't know your workflow, so the server teaches it. MCP's `InitializeResult.instructions` is pushed into the client's system prompt on connect, and this server uses it to establish the working method rather than just the mechanics: **compose procedurally instead of hand-writing SVG** (place primitives, then let Inkscape align, distribute, boolean and clone them), **rasterize and actually look at the result** before declaring it done, **ask you to select** the objects you want help with, and **open the dialog or tool** you're asking about instead of describing a menu path.
  124. Deeper material is pull-based — `resource://inkscape/mcp-workflow` (operational guide, recipes, and the Inkscape rendering pitfalls that silently ruin output), `resource://inkscape/cli-actions` and `resource://inkscape/gui-actions` (the full action catalog), plus `prompt://inkscape/design-workflow` for the step-by-step design loop, which most clients surface as a slash command. The pushed instructions name those explicitly so the agent knows to fetch them.
  125. ## Learn more
  126. - [docs/INSTALL.md](docs/INSTALL.md) — full install walkthrough.
  127. - [docs/TOOLS.md](docs/TOOLS.md) — every operation per tool.
  128. - [docs/TROUBLESHOOTING.md](docs/TROUBLESHOOTING.md) — when things break.
  129. - [src/inkscape_mcp/reference/](src/inkscape_mcp/reference/) — captured Inkscape 1.4.4 `--action-list`, the GUI-only window/document actions, and `--help`; ships in the wheel and is served as `resource://inkscape/cli-actions` / `gui-actions` / `cli-help`.
  130. ## Star history
  131. [![Star History Chart](https://api.star-history.com/svg?repos=aravindev/inkscape_mcp&type=Date)](https://star-history.com/#aravindev/inkscape_mcp&Date)
  132. ## Support
  133. If you like my work and found this useful, feel free to support me at [buymeacoffee.com/aravindev](https://buymeacoffee.com/aravindev).
  134. <a href="https://buymeacoffee.com/aravindev">
  135. <img src="https://raw.githubusercontent.com/aravindev/inkscape_mcp/main/assets/buymeacoffee-qr.png" alt="Buy me a coffee QR code" width="180">
  136. </a>
  137. ## License
  138. MIT — see [`LICENSE`](LICENSE). This project is a fork of upstream MIT-licensed work; attribution and lineage details are in [`NOTICE.md`](NOTICE.md).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.