Skip to main content
Glama
Sign In
TheStreamCode

chutes-media-mcp

by TheStreamCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CHUTES_WARMUPNoWarm models up before invoking.true
CHUTES_API_KEYYesYour Chutes API key.
CHUTES_OUTPUT_DIRNoOutput directory relative to the agent's CWD.assets/chutes
CHUTES_AUTH_SCHEMENoHow the key is sent in Authorization: raw or bearer.raw
CHUTES_API_BASE_URLNoManagement API base URL.https://api.chutes.ai
CHUTES_COLD_START_RETRIESNoRetries when a cold model returns 503 no-instances.4
CHUTES_PROGRESS_INTERVAL_MSNoHow often progress heartbeats are emitted.5000
CHUTES_COLD_START_BACKOFF_MSNoBase backoff between cold-start retries.8000

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_media_modelsA

List 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_modelA

Fetch 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_mediaA

Run 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//) and the saved path is returned. Long video/music jobs block with progress updates.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored across 3 tools

Disambiguation5/5

The three tools form a clear discovery-to-execution pipeline: list models, inspect a model's schema, then generate. Each has a distinct purpose and the descriptions explicitly guide sequencing, leaving little room for misselection.

Naming Consistency5/5

All tool names use consistent snake_case with verb-led phrasing: list_media_models, describe_media_model, generate_media. The pattern is predictable and readable throughout.

Tool Count5/5

Three tools are well-scoped for a media-generation workflow: discovery, schema inspection, and generation. Each tool earns its place, and the set avoids unnecessary surface area.

Completeness4/5

The core workflow is covered: list models, inspect live schemas, and generate/save assets with progress updates. Minor gaps exist around asset management or job cancellation/status, but the main generation lifecycle is complete enough for agents to work with.

Maintenance

ActivityActive
ResponsivenessNo issues

Resources