Skip to main content
Glama
code-and-crypto

inkscape-mcp-server

by code-and-crypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to inkscape-mcp-server

No user-submitted related servers found.

    Related Servers

    • inkscape-mcp

      GianluDeveloper
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP agents to create and edit SVG files, inspect documents, export previews, and insert editable artwork into a running Inkscape desktop session.
      MIT

    • mcpinkscape

      tspspi
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      4
      BSD 3-Clause

    • inkscape-mcp

      Berrio
      A
      license
      B
      quality
      B
      maintenance
      Enables headless and secure control of Inkscape for creating, inspecting, and resizing SVG documents, and exporting to PNG, PDF, and SVG with validation of size, pages, structure, and hashes.
      19
      MIT

    • Inkscape MCP Server

      ws-buntu
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to create, inspect, validate, and export SVG designs using Inkscape CLI through MCP tools.
      1
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools are cleanly separated by subsystem (paths, objects, SVG document, export, raw actions), and the prefix helps agents route. A few adjacent tools could be confused—object_clone vs object_compose's clone operation and svg_validate vs svg_analyze's quality checks—but the descriptions draw enough of a boundary.

    Naming Consistency4/5

    The set is uniformly lowercase snake_case with a domain prefix (object_, path_, svg_, export_, action_), which reads predictably. It is not a strict verb_noun pattern throughout—path_geometry, server_info, and path_effect are noun/adjective entries—so it falls just short of perfect consistency.

    Tool Count3/5

    At 23 tools the surface is in the heavy range for an MCP server, and an agent must digest a large catalog before acting. The breadth is defensible because Inkscape is a huge domain and each tool packages many underlying operations, but several aggregator tools could have been split or trimmed.

    Completeness4/5

    Core workflows—querying, editing, styling, path operations, document structure, optimization, export—are well covered, and action_run/extension_run provide escape hatches for the long tail of Inkscape actions. Obvious lifecycle gaps remain (no dedicated document load/save or object creation/deletion tool), but they can often be worked around through raw actions or existing file context.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive

    Resources