MCP Server

MCP server for Draw Things - local AI image generation on Mac. Exposed over MCP by the mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

An MCP (Model Context Protocol) server for Draw Things - enabling LLMs to generate images locally on Mac using Stable Diffusion and other AI models.

• Text-to-Image Generation — - Generate images from text prompts using the currently loaded model in Draw Things
• Image-to-Image Transformation — - Transform existing images using text prompts
• Configuration Access — - Query the current Draw Things settings and loaded model
• Local Processing — - All image generation runs locally on your Mac using Apple Silicon (M1/M2/M3/M4)

Adding it to your client

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

Its toolset

Everything the assistant can do here goes through one of these:

• Cursor — The Cursor tool exposed by this server
• check_status — Check if the Draw Things API server is running and accessible
• get_config — Get the current Draw Things configuration including the loaded model and settings
• generate_image — The generate_image tool exposed by this server
• transform_image — The transform_image tool exposed by this server

Configuration

You will need one environment variable: DRAWTHINGS_HOST. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• macOS with Apple Silicon (M1/M2/M3/M4) - Draw Things app installed - Node.js 18 or later

Caveats

• 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.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.

When to reach for it

This sits in the AI and media services group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP's toolset — Cursor, check_status, get_config and 2 more — is a fair guide to whether it matches your workflow. It is maintained by james-see; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.