Chutes Media MCP vs Mediamcp
A side-by-side look at the Chutes Media MCP and Mediamcp 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 Mediamcp 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 Mediamcp when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
OPENROUTER_API_KEY. - You want tools like
generate_image, edit_image, generate_video.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 60/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | CHUTES_API_KEYCHUTES_AUTH_SCHEMECHUTES_API_BASE_URLCHUTES_OUTPUT_DIRCHUTES_WARMUPCHUTES_COLD_START_RETRIESCHUTES_COLD_START_BACKOFF_MSCHUTES_MAX_ASSET_MB | OPENROUTER_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 4 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 3 | 6 |
| Full listing | View Chutes Media MCP | View Mediamcp |
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.
Mediamcp tools 6
generate_imageGenerate one or more images from a text prompt using a cloud AI model. Every image is saved to disk and its absolute path is returned, along with a small inline preview. Use edit_image instead when starting from an existing image.edit_imageEdit or transform existing image(s) with a text instruction — restyle, add or remove elements, change background, or combine several images into one scene. The result is saved to disk and its absolute path is returned, along with a small inline preview.generate_videoGenerate a video from a text prompt, and optionally from an input image (image-to-video). Async job: starts generation, then waits and polls. Video generation typically takes 1-5 minutes. The finished file is saved to disk and its absolute path is returned. If waiting times out, a polling_url is returned — pass it to check_video_status later instead of starting a new (billed) job. For image-to-video, pass first_frame_image so the clip animates from that exact picture (e.g. a still produced by generate_image). Image inputs require an image-to-video-capable model such as 'bytedance/seedance-2.0', 'bytedance/seedance-2.0-fast', or 'google/veo-3.1'.check_video_statusCheck a previously started video generation job (from generate_video's polling_url or video id). If the job has completed, downloads the video, saves it to disk, and returns the absolute path.list_modelsList image- and video-capable model slugs available on the configured endpoint, with pricing where known. Use this to pick a `model` value for generate_image, edit_image, or generate_video.check_configDiagnose the mediamcp server setup: endpoint, API key presence and validity, default models, and output directory writability. Run this first when any other mediamcp tool fails.
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"
}
}
}
}
Mediamcp
{
"mcpServers": {
"legolev-mediamcp": {
"command": "npx",
"args": [
"-y",
"mediamcp"
],
"env": {
"OPENROUTER_API_KEY": "YOUR_OPENROUTER_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Chutes Media MCP is categorized under Multimedia Process and uses a local stdio subprocess. Mediamcp belongs to Multimedia Process and uses a local stdio subprocess. Pick Chutes Media MCP for multimedia process work and Mediamcp 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. Mediamcp is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 legolev-mediamcp 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. Mediamcp has 64/100 (Good) with 2 views, 0 installs and 4 GitHub stars.