Chutes Media MCP vs PixelDojo
A side-by-side look at the Chutes Media MCP and PixelDojo MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Chutes Media MCP for multimedia process work as a local process; choose PixelDojo for multimedia process as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Chutes Media MCP when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CHUTES_API_KEY, CHUTES_AUTH_SCHEME, CHUTES_API_BASE_URL, CHUTES_OUTPUT_DIR, CHUTES_WARMUP, CHUTES_COLD_START_RETRIES, CHUTES_COLD_START_BACKOFF_MS, CHUTES_MAX_ASSET_MB. - You want tools like
list_media_models, describe_media_model, generate_media.
Choose PixelDojo when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PIXELDOJO_API_KEY. - You want tools like
pixeldojo_generate, pixeldojo_edit, pixeldojo_character.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 60/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | CHUTES_API_KEYCHUTES_AUTH_SCHEMECHUTES_API_BASE_URLCHUTES_OUTPUT_DIRCHUTES_WARMUPCHUTES_COLD_START_RETRIESCHUTES_COLD_START_BACKOFF_MSCHUTES_MAX_ASSET_MB | PIXELDOJO_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | 14 |
| Full listing | View Chutes Media MCP | View PixelDojo |
Tools & capabilities
Chutes Media MCP tools 3
list_media_modelsList available Chutes media-generation models (image / video / music / speech), optionally filtered by kind or a free-text query. Use this to discover a model, then call describe_media_model before generate_media.describe_media_modelFetch a model's live cords and input schemas so you can compose a valid request. ALWAYS call this before generate_media for an unfamiliar model. Returns every cord (e.g. generate, and img2img/inpaint when present) with its required fields, types, defaults and a minimal example payload.generate_mediaRun a generation and save the asset into the workspace. `params` is the payload you composed from describe_media_model. For editing, `params` may reference workspace file paths (e.g. image, mask) which the server reads and encodes. The asset is saved under output_dir (default ./assets/chutes/<kind>/) and the saved path is returned. Long video/music jobs block with progress updates.
PixelDojo tools 14
pixeldojo_generateAny prompt to an image or video. Defaults to Seedream for stills; pass any model id for video and more.pixeldojo_editChange existing images with a text instruction, multi-image capable.pixeldojo_characterConsistent characters across shots.pixeldojo_storyboardOne video shot from a scene brief.pixeldojo_filmFilm Studio: a multi-shot film from an idea, or a music video synced to your song.pixeldojo_videoChange, move or extend an existing clip.pixeldojo_episodeFaceless Studio: a narrated video episode from a topic.pixeldojo_adMarketing Studio: a product video ad from a URL or product images.pixeldojo_from_urlProduct page URL to structured product info. Free.pixeldojo_upscaleEnhance an image up to 16x or a video up to 4K.pixeldojo_audioDialogue, effects and music in one clip.pixeldojo_librarySearch your saved media and recent generations.- +2 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Chutes Media MCP
{
"mcpServers": {
"chutes-media-mcp": {
"command": "npx",
"args": [
"-y",
"chutes-media-mcp"
],
"env": {
"CHUTES_API_KEY": "YOUR_CHUTES_API_KEY_HERE",
"CHUTES_AUTH_SCHEME": "YOUR_CHUTES_AUTH_SCHEME_HERE",
"CHUTES_API_BASE_URL": "YOUR_CHUTES_API_BASE_URL_HERE",
"CHUTES_OUTPUT_DIR": "YOUR_CHUTES_OUTPUT_DIR_HERE",
"CHUTES_WARMUP": "YOUR_CHUTES_WARMUP_HERE",
"CHUTES_COLD_START_RETRIES": "YOUR_CHUTES_COLD_START_RETRIES_HERE",
"CHUTES_COLD_START_BACKOFF_MS": "YOUR_CHUTES_COLD_START_BACKOFF_MS_HERE",
"CHUTES_MAX_ASSET_MB": "YOUR_CHUTES_MAX_ASSET_MB_HERE"
}
}
}
}
PixelDojo
{
"mcpServers": {
"pixeldojo": {
"command": "npx",
"args": [
"-y",
"@pixeldojo/mcp"
],
"env": {
"PIXELDOJO_API_KEY": "YOUR_PIXELDOJO_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Chutes Media MCP is categorized under Multimedia Process and uses a local stdio subprocess. PixelDojo belongs to Multimedia Process and uses a local stdio subprocess. Pick Chutes Media MCP for multimedia process work and PixelDojo for multimedia process.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Chutes Media MCP has no declared pricing — check the project's own site. PixelDojo has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add chutes-media-mcp and pixeldojo as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Chutes Media MCP has a quality signal of 60/100 (Good) with 1 views, 0 installs and 1 GitHub stars. PixelDojo has 56/100 (Good) with 0 views, 0 installs and 0 GitHub stars.