Modelflare MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MODELFLARE_LOCALE | No | Locale for error messages: `en` (default) or `zh`. | |
| MODELFLARE_API_KEY | Yes | Your Modelflare Smart API Key (required). | |
| MODELFLARE_BASE_URL | No | The Modelflare API base URL. `global` maps to https://modelflare.dev/v1 (default), `china` maps to https://origin.modelflare.dev/v1, or you can provide a custom URL. | |
| MODELFLARE_OUTPUT_DIR | No | Directory where images and videos are saved. Default is ./modelflare-output. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_modelsA | Lists the models this Modelflare API key can call, with the docs page that holds each media model's exact request contract. Defaults to image and video models. |
| generate_imageA | Generates an image, or edits one with edit=true, using a Modelflare image model, and saves the result to the output directory. Billed to the Modelflare balance by actual usage. |
| create_videoA | Starts an asynchronous Modelflare video task and returns its task ID. Poll with get_video_status and save with download_video. Billed to the Modelflare balance by actual usage. |
| get_video_statusC | Returns the status and progress of a Modelflare video task. |
| download_videoA | Saves a completed Modelflare video to the output directory. Optionally waits for the task first. Result URLs expire, so download soon after completion. |
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 covers a distinct step: create_video (start task), get_video_status (poll), download_video (save), generate_image (image gen/edit), list_models (discovery). The only mild overlap is download_video optionally waiting for a task, which partially duplicates get_video_status, but descriptions clearly delineate roles.
All five tools follow a clean verb_noun snake_case pattern (create_video, download_video, generate_image, get_video_status, list_models). The convention is applied uniformly with no deviations.
Five tools is well-scoped for a media generation API, covering video task lifecycle, image generation, and model discovery. Each tool earns its place with no redundancy.
Core lifecycle is covered: create/status/download for video and generate/edit for image, plus model listing. Minor gaps exist (no cancel_task, no list_tasks, and no image status polling), but primary workflows are fully supported.