Skip to main content
Glama
eduardoabreu81

Forge Neo MCP

by eduardoabreu81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Forge Neo MCP

No user-submitted related servers found.

    Related Servers

    • local-genai-mcp

      makoyuki
      A
      license
      B
      quality
      C
      maintenance
      Enables Claude Code to call local generative AI services on a LAN, letting users list and chat with Ollama models and list checkpoints, LoRAs, and samplers or generate and save images via Stable Diffusion WebUI Forge Neo. Requests can be made in natural language, with per-call options for model, image size, and Hires.fix settings.
      1
      MIT

    • forge-mcp

      danmarce
      A
      license
      A
      quality
      B
      maintenance
      Exposes a local Forge or AUTOMATIC1111 SDXL backend as typed image-generation tools, enabling any MCP client to generate and edit images through a deterministic, stateless interface with server-enforced SFW content.
      3
      Mozilla Public 2.0

    • invokeai-mcp

      sandraschi
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to control a local InvokeAI creative engine, supporting text-to-image, image-to-image, masked inpaint, upscaling, and full queue, model, gallery, board, and workflow management.
      13
      2
      MIT

    • gemini-image-mcp

      nguyennamkkb
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to generate images through Gemini running inside the user's own browser, returning results as image files (optionally inlined for display). It also manages the local bridge lifecycle with status, start, and stop tools, plus reference-image prompting and aspect-ratio control.
      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 10 tools

    Disambiguation4/5

    Tools are mostly distinct by resource and action—LoRA search vs detail, module check vs download, generation vs progress—but model_profile and prompt_dialect overlap on prompt dialect, and models/model_profile could be confused at a glance. The detailed descriptions mitigate most ambiguity.

    Naming Consistency4/5

    Names consistently use lowercase snake_case and a readable resource-oriented style (loras, lora_info, models, module_check). Not all are verb_noun—generate is a bare verb and progress is ambiguous—so it is not a perfect 5, but there is no chaotic convention mixing.

    Tool Count5/5

    Ten tools is well within the ideal 3–15 range and matches the server's scope: discovery, model/prompt/LoRA/module setup, generation, and progress control. No tool feels redundant or superfluous.

    Completeness4/5

    The surface covers the full generation workflow—model loading, profiling, prompt dialect, LoRA lookup, module diagnostics/download, generate, and progress monitoring. Minor gaps exist (no LoRA download/management, no explicit output/history listing), but they are not required for the core purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources