Agnes Media MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGNES_API_KEY | Yes | Agnes AI API Key | |
| AGNES_BASE_URL | No | API 网关地址 | https://apihub.agnes-ai.com |
| AGNES_OUTPUT_DIR | No | 覆盖输出根目录（设置后图片→<dir>/images、视频→<dir>/videos） |
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 |
|---|---|
| agnes_generate_imageA | Generate an image with Agnes Image 2.1 Flash. Text-to-image by default; pass image_urls to do image-to-image (transform/restyle while preserving composition). The result is saved to the local output directory and a preview is returned inline. |
| agnes_generate_videoA | Start an Agnes Video V2.0 generation (async). Text-to-video by default; pass image_url for image-to-video, or keyframe_urls (2+) for keyframe transitions. Video generation takes minutes, longer than an MCP request can block. This tool creates the task and waits up to wait_seconds for it to finish: if it completes in time, the mp4 is downloaded locally and its path returned; otherwise it returns the video_id immediately — poll agnes_get_video_status with that id (download:true) to fetch the result when ready. Duration = num_frames / frame_rate. num_frames must be <=441 and of the form 8n+1. |
| agnes_get_video_statusA | Check the status of an Agnes video task by video_id. Returns status/progress, and if completed, the remote URL. Optionally downloads the mp4 locally when ready. |
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 3 tools
Each tool targets a distinct operation: image generation, video generation (async), and video status retrieval. No overlap in purpose.
All tools follow a consistent 'agnes_verb_noun' pattern with underscores (e.g., generate_image, get_video_status). No mixing of styles.
3 tools is minimal but appropriate for the focused scope of image and video generation. Could be expanded with list/delete utilities, but not underpowered.
Covers core generation and status polling, but lacks list/delete or cancel operations for videos, and no tool for managing images beyond generation.