Draw Things MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DRAWTHINGS_HOST | No | API server host | localhost |
| DRAWTHINGS_PORT | No | API server port | 7860 |
| DRAWTHINGS_OUTPUT_DIR | No | Image save directory | ~/Pictures/drawthings-mcp |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_statusA | Check if the Draw Things API server is running and accessible |
| get_configA | Get the current Draw Things configuration including the loaded model and settings |
| generate_imageA | Generate an image from a text prompt using the Draw Things app. The image will be saved to disk and the file path returned. |
| transform_imageA | Transform an existing image using a text prompt (img2img). Either image_path or image_base64 must be provided. |
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 4 tools
Each tool has a clearly distinct purpose: status checking, configuration retrieval, text-to-image generation, and image-to-image transformation. There is no meaningful overlap between any pair of tools.
All tool names follow a consistent verb_noun pattern: check_status, get_config, generate_image, transform_image. The naming style is uniform and predictable.
Four tools is a well-scoped count for an image generation server. Each tool covers an essential operation without unnecessary redundancy or bloat.
The core workflow of checking server status, viewing configuration, generating images, and transforming images is covered. A possible minor gap is the lack of a tool to update configuration or switch models, but this does not block the primary use case.