Skip to main content
Glama
AceDataCloud

mcp-minimax

by AceDataCloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ACEDATACLOUD_API_TOKENYesYour AceDataCloud API token

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
minimax_list_modelsB

Describe the MiniMax H3 model and supported input modes.

minimax_list_actionsA

List MiniMax H3 generation and task tools.

minimax_list_tasksA

List video generation tasks, optionally filtered by creation timestamp.

minimax_get_taskA

Query the status and result of a video generation task.

Use this to check if a generation is complete and retrieve the resulting
video URLs and other metadata.

Use this when:
- You want to check if a generation has completed
- You need to retrieve video URLs from a previous generation
- You want to get the full details of a generated video

Task states:
- 'queued' or 'running': Generation is still in progress
- 'succeeded': Generation finished successfully
- 'failed' or 'cancelled': Generation reached a terminal error state

Returns:
    Task status and generated video information including URLs and status.
minimax_get_tasks_batchA

Query multiple video generation tasks at once.

Efficiently check the status of multiple tasks in a single request.
More efficient than calling minimax_get_task multiple times.

Use this when:
- You have multiple pending generations to check
- You want to get status of several videos at once
- You're tracking a batch of generations

Returns:
    Status and video information for all queried tasks.
minimax_delete_taskB

Delete a MiniMax video generation task.

minimax_generate_video_from_textB

Generate a MiniMax H3 video from a text prompt.

minimax_generate_video_from_imagesA

Generate from one first-frame image or multiple reference images.

Single image uses first_frame mode; multiple images use reference_image mode.
The two modes are mutually exclusive per MiniMax H3 v2 API contract.
minimax_generate_video_from_audioA

Generate a MiniMax H3 video guided by audio and reference images.

Audio-guided generation uses reference mode exclusively (reference_audio
forces the entire content into reference-to-video mode per the H3 v2 contract).
minimax_generate_videoD

Generate a video from the full MiniMax content schema.

Prompts

Interactive templates invoked by user choice

NameDescription
minimax_video_generation_guideGuide tool selection for MiniMax H3 video generation.
minimax_workflow_examplesShow common MiniMax H3 workflows.
minimax_prompt_suggestionsProvide MiniMax H3 prompt-writing guidance.

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

A3.5/5.0

Scored across 10 tools

Disambiguation5/5

Each tool targets a distinct operation: discovery (list_models, list_actions), task management (list_tasks, get_task, get_tasks_batch, delete_task), and generation (text/images/audio/full schema). Even the similar generation tools are clearly separated by input type and explicit mode constraints.

Naming Consistency5/5

All tools follow a strict snake_case verb_noun pattern with a consistent 'minimax_' prefix. The pattern is uniform: list_*, get_*, delete_*, generate_video_from_*. Minor differences like get_tasks_batch still match the convention.

Tool Count5/5

Ten tools is well-scoped for a video generation server. Each tool covers a necessary part of the workflow—discovery, generation (four input modes), tracking, and deletion—without redundant or superfluous entries.

Completeness5/5

The tool surface provides complete lifecycle coverage: describe capabilities, generate videos from all supported input types, query single/batch tasks, and delete tasks. No obvious dead ends or missing critical operations for the stated domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources