A
licenseB
qualityA
maintenanceEnables driving Inkscape headlessly from an MCP client, with verified SVG editing, rendering, optimization, and animation tools.
23
MIT
inkscape-mcp
by Berrio
Related Servers
Alternatives to inkscape-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to inspect, edit, validate, render, and export SVG/Inkscape documents safely with reversible operations and risk-classed tools.873MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to create, inspect, edit, render, and export SVG/Inkscape documents through typed drawing tools, with a deterministic offline backend and an optional bridge to a locally running Inkscape instance for limited live editing and snapshots.BSD 3-Clause
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create, inspect, validate, and export SVG designs using Inkscape CLI through MCP tools.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables creation, validation, rendering, and optimization of SVG images with conversion capabilities to PNG, React components, React Native components, and Data URIs.-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to control Inkscape for vector graphics editing via MCP tools.62MIT
TDQS
B3.4/5.0
Scored across 19 tools
Disambiguation4/5
The tools are mostly organized by clear resource prefixes (elements_, document_, workspace_, export_), and each action targets a distinct operation. A few document-level tools (resize vs settings vs pages) touch related page concepts, but their descriptions distinguish geometry changes from display settings and multi-page editing.
Naming Consistency4/5
Most names follow a predictable snake_case resource-plus-action pattern, especially elements_* and document_*. The export_* tools invert that pattern (verb plus format) and workspace_list_documents is a slightly awkward compound, so naming is not perfectly uniform but remains readable.
Tool Count3/5
Nineteen tools is a heavy surface for an MCP server, falling in the 16-25 range that feels borderline. The breadth is understandable because the server covers documents, elements, workspaces, exports, and status, but not every tool feels strictly necessary.
Completeness4/5
The set covers the core SVG document and element lifecycle: create, query/update, delete, group, arrange, transform, page-level changes, and PNG/PDF/SVG export. Obvious gaps such as explicit layer CRUD, path-level editing, and arbitrary SVG import remain, but they can be worked around with the bounded query/export tools.
Maintenance
ActivityMaintained
ResponsivenessNo issues