Skip to main content
Glama
sandraschi

invokeai-mcp

by sandraschi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to invokeai-mcp

No user-submitted related servers found.

    Related Servers

    • ComfyUI MCP Server

      jaewilson07
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to generate and iteratively refine images, audio, and video by interacting with a local ComfyUI instance through natural conversation. It provides comprehensive tools for workflow management, node introspection, and publishing generated assets.
      Apache 2.0

    • Forge Neo MCP

      eduardoabreu81
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to generate images on a local Stable Diffusion Forge Neo instance, automatically inferring prompt style and sampling parameters from the user's setup and past generations, and providing tools for LoRA search, model management, and module checks.
      10
      1
      MIT

    • Krita Illustration MCP

      xqqcylh6780
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI models to directly control a local Krita instance by inspecting real canvas previews, managing documents and layers, importing and masking generated images, inpainting, painting with the brush engine, checkpointing, and exporting KRA/PNG files.
      MIT
    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

    A3.9/5.0

    Scored across 13 tools

    Disambiguation4/5

    Each tool targets a distinct domain (queue, gallery, models, generation, workflows, boards, system), and the operation-based tools (invokeai_generate, invokeai_queue) are clearly separated. Minor overlap exists between show_invokeai_dashboard_card and invokeai_system (both report health/version), but descriptions mitigate confusion.

    Naming Consistency3/5

    Naming is inconsistent: four tools use a 'show_invokeai_*_card' pattern while the rest use bare 'invokeai_*' nouns with operation parameters. Some tools are verb-like (invokeai_help, invokeai_shutdown), others are noun-objects (invokeai_gallery, invokeai_boards), making the pattern unpredictable.

    Tool Count5/5

    13 tools is well within the ideal range for a server covering a rich creative domain. Each tool addresses a distinct area (generation, queueing, model management, gallery, workflows, system), and the card-based display tools serve as convenient views rather than redundant functionality.

    Completeness4/5

    Core workflows are well covered: generation includes txt2img, img2img, inpaint, and upscale; queue handles lifecycle and result retrieval; models support CRUD; gallery and boards manage images; workflows have full CRUD. Minor gaps exist (e.g., no explicit single-image delete outside 'manage' operations, and no batch generation interface), but agents can accomplish tasks without major dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources