Recraft MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | No | Your RunAPI API key. Alternatively, set it in ~/.config/runapi/config.json. |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginA | Authenticate RunAPI by opening a browser PKCE login flow and saving the API key to ~/.config/runapi/config.json. |
| remove_backgroundB | Create a Recraft task on RunAPI (remove background). Returns a task id, status, and output URLs. |
| upscale_imageC | Create a Recraft task on RunAPI (upscale image). Returns a task id, status, and output URLs. |
| get_taskB | Fetch the current status and latest result payload for a recraft task. |
| check_pricingC | Look up RunAPI pricing for the recraft model line. |
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 5 tools
Each tool has a clearly distinct purpose: remove_background and upscale_image are non-overlapping image operations, while get_task, check_pricing, and login serve separate functions. No two tools could be confused.
Four of five tools follow a clean verb_noun snake_case pattern (remove_background, upscale_image, get_task, check_pricing). The only deviation is 'login', which is a single word acting as both noun and verb, but overall consistency is strong.
Five tools is a well-scoped number, each earning its place for task creation, status checking, pricing, and authentication. It is slightly thin for a full Recraft platform integration, but reasonable for a focused RunAPI wrapper.
Despite being named 'Recraft MCP Server', the surface exposes only two image operations (background removal and upscaling) out of Recraft's broader capabilities, and lacks task listing, cancellation, or core generation features like image creation and vectorization. These are significant gaps for the apparent domain.