Skip to main content
Glama
skelly-77

openrouter-image-mcp

by skelly-77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to openrouter-image-mcp

No user-submitted related servers found.

    Related Servers

    • img

      timpulver
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code to generate and iteratively refine images through OpenAI's Responses API, branching from any earlier image by its short id and using pasted screenshots, local files, URLs, or library images as references. Results are previewed in a live local gallery and stored in an iCloud-synced library with JSON sidecars for prompts, lineage, and usage.
      MIT

    • Z-Image Studio MCP Server

      LinaJenkins
      F
      license
      Not graded
      quality
      A
      maintenance
      Exposes tools for local text-to-image generation, listing available models, and browsing past generations over the Model Context Protocol, with stdio entrypoints plus SSE and Streamable HTTP transports so AI agents can create and retrieve images.
      -

    • pixelgate

      0-Br
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code to generate and edit images through two MCP tools, routing requests to GPT Image models via a local CLIProxyAPI gateway using a ChatGPT subscription, with input validation and artifacts/receipts written to a specified directory.
      MIT

    • openrouter-media

      serral
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes OpenRouter's image generation, video generation, image-to-video, and model discovery to local AI clients such as Claude Code, OpenCode, OMP, and Codex over stdio. It lets clients list available models, generate images and videos, track and download video jobs, and resume in-flight jobs without blocking past client tool timeouts.
      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

    A4.3/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool maps to a clearly distinct action: auth_login/auth_logout are opposite operations, account_status is a read-only check, list_image_models vs get_image_model cleanly separate browsing from detail lookup, and generate_image vs edit_image separate creation from modification. No meaningful overlap exists.

    Naming Consistency4/5

    Most tools follow a readable verb_noun pattern (list_image_models, get_image_model, generate_image, edit_image, auth_login, auth_logout). Minor deviation: the auth group mixes prefixes ('auth_' for login/logout vs 'account_' for status), but it remains predictable.

    Tool Count5/5

    Seven tools is well-scoped for an image-generation service: three for auth/session, two for model discovery, two for generation/editing. Every tool earns its place with no redundancy or bloat.

    Completeness5/5

    The surface covers the full lifecycle: sign in, verify session/spend, sign out, discover models, inspect model details, and both generate and edit images with rich parameter control. No obvious gaps for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources