inkscape_mcp
Related Servers
Alternatives to inkscape_mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables driving Inkscape headlessly from an MCP client, with verified SVG editing, rendering, optimization, and animation tools.23MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to control Inkscape for vector graphics editing via MCP tools.102MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that lets AI assistants control Adobe Illustrator locally—running ExtendScript, capturing canvas screenshots, exporting artwork, and optionally remembering techniques—all without network activity.-
- AlicenseAqualityCmaintenanceMCP server that turns AI into an SVG artist. One rendering engine with a rich JSON schema, AI controls all design parameters. Renders animated SVGs with CSS @keyframes and SMIL animations. Supports 16+ element types, parametric curves, pattern groups, gradient/filter/clip/mask definitions, and PNG preview. No external dependencies, runs locally via npx.3127 npm31MIT
- AlicenseAqualityBmaintenanceAn MCP server that lets an AI (Claude Desktop, Claude Code, Cursor, …) draw and edit plane-geometry figures directly on GeoGebra Calculator (https://www.geogebra.org/calculator).1189 npmMIT
- AlicenseAqualityDmaintenanceA minimal MCP server for AI-driven canvas manipulation and visualization using tldraw. It enables AI clients to programmatically create, update, and manage shapes, flowcharts, and frames on a live interactive canvas.92MIT
TDQS
Scored across 8 tools
The live-vs-headless split is explicitly documented, which helps, but several tool pairs still overlap: validate appears in both inkscape_file and inkscape_analysis, dimensions/object inspection is spread across inkscape_analysis, inkscape_vector (query_document/measure_object) and inkscape_live (inspect_*), and export/convert is split between inkscape_file and inkscape_vector (render_preview/export_dxf). Most confusingly, inkscape_extension (discover/invoke extensions) competes with inkscape_system's list_extensions/execute_extension with no guidance on which to use. An agent must read carefully to avoid misselection.
All tools follow a clean inkscape_<category> namespace (live, extension, file, vector, analysis, system, gradient, metadata) with no mixing of camelCase or verb styles. Minor deviation: the categories mix adjectives ('live') and nouns, and are abstract buckets rather than action names, so the name alone doesn't reveal the operations. Still highly consistent and predictable.
Eight portmanteau tools is a well-scoped surface for a rich GUI+CLI domain and avoids the tool explosion that single-purpose wrapping would create. The tradeoff is that several tools hide long operation lists (inkscape_live, inkscape_vector) whose contents must be discovered from descriptions rather than names.
Coverage is broad: file load/save/convert/validate, vector ops and booleans, live document editing, analysis, gradients, metadata, extensions, and system introspection. Gaps remain around shape/text primitives (no dedicated rect/circle/text creation) and explicit layer management beyond layers_to_files, but core SVG edit lifecycle is covered.