Skip to main content
Glama

Related Servers

Alternatives to gimp-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI models and external applications to control GIMP remotely via the Model Context Protocol, allowing image manipulation and object querying through natural language.
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Bridges GIMP image editing with AI assistants via the Model Context Protocol, enabling visual feedback and 56 tools for autonomous image workflows.
      GPL 3.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to create, paint, edit, inspect, and export images in a running GIMP 3.2 instance via MCP.
      106 PyPI
      GPL 3.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables controlling GIMP 3 locally through natural language, providing tools for image editing, layer management, selections, and PDB procedure invocation. Keeps all images and files on the user's machine with a local-first, secure design.
      40
      1
      GPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to control GIMP 2.10 through its Script-Fu server, providing access to the entire GIMP procedure database with a vision feedback loop for iterative editing.
      6
      AGPL 3.0
    • A
      license
      Not graded
      quality
      F
      maintenance
      MCP server that bridges GIMP 3.0 with natural language commands, enabling conversational image editing through Claude Desktop and other MCP clients. Exposes GIMP's full PyGObject API for AI-powered image manipulation.
      258
      GPL 3.0

    TDQS

    A3.5/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose. Even similar tools like fill_ellipse and fill_rect are differentiated by shape, and list_images vs get_image are different operations. The procedure.* tools are for PDB access and don't overlap with others.

    Naming Consistency5/5

    All tool names follow a consistent `gimp.<verb>_<noun>` pattern, with compound verbs like `get_context_state`. The sub-namespace for procedure tools (`gimp.procedure.*`) is also consistent.

    Tool Count5/5

    18 tools is well-scoped for a GIMP MCP server. It covers core image operations without being overwhelming, and the batch and procedure tools add flexibility without bloating the surface.

    Completeness5/5

    The tool set covers essential image operations (open, list, add text, draw shapes, fill, export, layer manipulation) and provides access to the entire GIMP PDB via `procedure.call`, making the surface effectively complete for any GIMP operation.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues