sd-api-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_imageA | Generate an image using Stable Diffusion. Waits for completion and returns the result. |
| inpaint_imageA | Inpaint an image using Stable Diffusion. Waits for completion and returns the result. |
| submit_generateA | Submit an image generation job without waiting. Returns the job ID for manual polling. |
| submit_inpaintA | Submit an inpainting job without waiting. Returns the job ID for manual polling. |
| batch_generateA | Submit a batch of image generation requests (up to 10). |
| compare_modelsA | Generate images from multiple models using the same prompt for comparison. |
| list_modelsB | List available models. |
| get_model_metadataA | Get metadata for a specific model from its safetensors header. |
| list_jobsA | List all jobs with their current status, progress, and timing information. |
| get_job_statusB | Get the current status and result of a specific job. |
| cancel_jobA | Cancel a pending or running job. |
| health_checkA | Check if the Stable Diffusion API is healthy and reachable. |
| system_infoA | Get system information including GPU device, dtype, model cache stats, and job queue stats. |
| list_schedulersA | List all available noise schedulers that can be used for image generation. |
| get_app_settingsA | Get the current application configuration parameters. |
| merge_modelsA | Merge two model checkpoints. Submits the job and waits for completion. |
| batch_merge_modelsA | Merge a base model with multiple target models in batch. Waits for completion. |
| recipe_mergeB | Execute a multi-step merge recipe. Each step merges the current result with a new target. Waits for completion. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Most tools target distinct operations (sync generation, async submission, batch, compare, merge variants), and descriptions clarify the differences. A few near pairs such as generate_image/submit_generate and batch_merge_models/recipe_merge could cause misselection, but the descriptions separate them well.
The dominant verb_noun pattern (list_models, get_job_status, merge_models) is readable, but there are notable deviations like health_check, system_info, recipe_merge, and submit_generate. The mix of verb-first and noun-first names is inconsistent enough to slow an agent down.
Eighteen tools is slightly above the ideal 3-15 range, but the breadth is justified by covering generation, async jobs, model metadata, system health, and model merging. It feels like a complete API surface rather than an inflated one.
The surface covers generation, inpainting, async job lifecycle, model listing/metadata, schedulers, and multiple merge workflows. Obvious gaps are minor, such as the lack of a general image-to-image tool or batch async variants, but core workflows have no dead ends.