Image Gen MCP Server

Most developer tooling work still happens through a UI a human drives. Image Gen MCP MCP server moves it into the conversation instead. Generate images using Automatic1111/ForgeUI API.

The short version

A MCP server that provides text-to-image generation capabilities using Stable Diffusion WebUI API (ForgeUI/AUTOMATIC-1111).

The tools it exposes

The server publishes 14 tools. What each one is for:

• generate_image — Generate images using Stable Diffusion
• Parameters — - prompt (required): Text description of the desired image
• negative_prompt — Things to exclude from the image
• steps — Number of sampling steps (default: 4, range: 1-150)
• width — Image width (default: 1024, range: 512-2048)
• height — Image height (default: 1024, range: 512-2048)
• cfg_scale — CFG scale (default: 1, range: 1-30)
• sampler_name — Sampling algorithm (default: "Euler")
• scheduler_name — Scheduler algorithm (default: "Simple")
• seed — Random seed (-1 for random)
• batch_size — Number of images to generate (default: 1, max: 4)
• restore_faces — Enable face restoration

What it needs from you

Configuration is passed through the environment: SD_WEBUI_URL, SD_AUTH_USER, SD_AUTH_PASS, SD_OUTPUT_DIR, SD_RESIZE_MODE, SD_UPSCALE_MULTIPLIER, SD_UPSCALE_WIDTH, SD_UPSCALE_HEIGHT. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js - Access to a Stable Diffusion WebUI instance with API enabled - The WebUI must have --api flag enabled when starting

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Image Gen MCP's toolset — generate_image, Parameters, negative_prompt and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Ichigo3766; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Image Gen MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.