Skip to main content
Glama
Congenital

sdnext_mcp

by Congenital
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to sdnext_mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • ComfyUI Local MCP Server

      AkiraVD
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to generate and edit images using local Stable Diffusion models in ComfyUI, with tools for text-to-image, img2img, ControlNet, UI frames, upscaling, and background removal—no cloud API or API key required.
      MIT

    • comfy-workflow-mcp

      PlateerLab
      F
      license
      Not graded
      quality
      A
      maintenance
      Exposes the workflows saved in a ComfyUI server (local, remote, or vast.ai) as MCP tools, letting agents list them, inspect their inputs, and run them with their own prompts, images, seeds, and per-run node toggles. It also reports server/GPU status, tracks and downloads job outputs, and uploads images or browses model folders.
      -
    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

    C2.9/5.0

    Scored across 125 tools

    Disambiguation2/5

    Many tools are unique resource/action pairs, but the set contains ambiguous clusters: legacy vs v2 CivitAI search, extra_network_detail vs extra_network_details, caption vs caption_dispatch vs tagger vs vqa vs analyze, and status vs progress. With 125 tools, agents are likely to mis-select despite good individual descriptions.

    Naming Consistency3/5

    The sdnext_ prefix and snake_case are consistent, and list_* verbs are used widely. However conventions drift: some names are resource nouns (sdnext_civitai_model, sdnext_browser_thumb, sdnext_latent_history), while others are verb_objects (sdnext_add_bookmark), and several list/action pairs (bookmarks vs add_bookmark, banned vs add_banned) are not uniform.

    Tool Count1/5

    125 tools is an extreme count for an MCP server. This is effectively a 1:1 wrapper for the full REST API, not a curated tool set, and would overwhelm any agent trying to select the right tool.

    Completeness4/5

    Coverage is impressively broad: model discovery, generation, control, image processing, captioning, CivitAI downloads, options, server management, and file operations are all represented. Minor gaps exist (e.g. no dedicated prompt-style CRUD or detailed history retrieval), but the generic sdnext_call_api fallback and delete_file cover most dead ends.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources