mcp-standardized text-to-speech synthesis with voice selection
Converts text input to audio output using MiniMax's text-to-audio API, exposed through the MCP protocol via a @mcp.tool decorated function. The server handles parameter marshaling, API authentication via region-specific endpoints (global vs mainland China), and returns either direct URLs or downloads audio files locally based on MINIMAX_API_RESOURCE_MODE configuration. Supports voice selection from a pre-defined voice list retrieved via list_voices tool.
Unique: Integrates MiniMax's TTS via MCP protocol with dual resource handling modes (URL vs local download) and region-aware API endpoint routing, enabling seamless voice synthesis within Claude Desktop and Cursor without custom API wrappers
vs alternatives: Simpler than building direct REST API clients for TTS because MCP abstraction handles authentication, transport, and resource management; more flexible than cloud-only TTS because local mode enables offline audio storage and compliance with data residency requirements
voice cloning from audio samples via mcp
Enables voice cloning by accepting audio file samples as input and generating a cloned voice model through MiniMax's voice_clone API. The server accepts audio files (WAV, MP3, or other formats supported by MiniMax), sends them to the API, and returns a voice_id that can be used with text_to_audio for subsequent synthesis. Implementation uses FastMCP's @mcp.tool decorator to expose the cloning function with parameter validation and error handling for malformed audio inputs.
Unique: Exposes MiniMax's voice cloning as an MCP tool, enabling voice model creation within Claude Desktop/Cursor workflows without direct API calls; integrates cloned voice_ids seamlessly with text_to_audio for immediate reuse
vs alternatives: More accessible than building custom voice cloning pipelines because MCP abstraction handles audio encoding and API communication; faster iteration than cloud-only TTS services because cloned voices persist in the MiniMax account for reuse
fastmcp-based tool registration and parameter validation
Leverages FastMCP framework's @mcp.tool decorator pattern to register tools with automatic parameter validation, type hints, and schema generation. Each tool (text_to_audio, generate_video, text_to_image, etc.) is defined as a Python function with type-annotated parameters, and FastMCP automatically generates JSON schemas for MCP clients. The framework handles parameter marshaling, type coercion, and validation errors, reducing boilerplate code and ensuring consistent tool interfaces across all capabilities.
Unique: Uses FastMCP's @mcp.tool decorator for automatic parameter validation and JSON schema generation, reducing boilerplate and ensuring consistent tool interfaces across all generation capabilities
vs alternatives: Simpler than manual schema writing because FastMCP generates schemas from type hints; more maintainable than hardcoded validation because parameter constraints are defined once in function signatures
client integration configuration for claude desktop and cursor
Provides documented configuration patterns for integrating the MCP server with Claude Desktop and Cursor via configuration files. For Claude Desktop, the server is configured in the Claude configuration JSON file with stdio transport and Python executable path. For Cursor, configuration is added through Cursor Settings > MCP > Add new global MCP Server. The server abstracts integration details, enabling clients to add the server without understanding MCP protocol internals. Configuration includes API key and region settings passed as environment variables.
Unique: Provides documented configuration patterns for Claude Desktop and Cursor integration, enabling users to add MiniMax capabilities without understanding MCP protocol details; supports environment variable-based API key configuration
vs alternatives: More accessible than building custom MCP clients because Claude Desktop and Cursor provide UI for tool discovery; simpler than direct API integration because MCP abstraction handles authentication and transport
text-to-image generation with prompt-based synthesis
Generates images from text prompts using MiniMax's image generation API, exposed via MCP @mcp.tool decorator. The server accepts a text prompt, sends it to MiniMax's image generation endpoint, and returns either a URL to the generated image (default) or downloads it locally based on MINIMAX_API_RESOURCE_MODE. Supports region-specific API routing and handles image format negotiation with the backend API.
Unique: Integrates MiniMax's image generation as an MCP tool with dual resource modes (URL vs local storage) and region-aware API routing, enabling image synthesis directly within Claude Desktop/Cursor without external image generation tools
vs alternatives: Simpler than managing separate image generation APIs because MCP handles authentication and transport; more flexible than web-based image generators because local mode enables offline storage and data residency compliance
text-to-video generation with prompt-based synthesis
Generates videos from text prompts using MiniMax's video generation API, exposed via MCP @mcp.tool decorator. The server accepts a text prompt describing desired video content, sends it to MiniMax's video generation endpoint, and returns either a URL to the generated video or downloads it locally. Handles region-specific API routing and manages video file format negotiation with the backend. Video generation is asynchronous and may require polling or callback mechanisms for completion status.
Unique: Exposes MiniMax's video generation as an MCP tool with dual resource modes and region-aware routing, enabling video synthesis within Claude Desktop/Cursor; handles asynchronous generation with URL or local file output
vs alternatives: More accessible than building custom video generation pipelines because MCP abstraction handles API communication and resource management; faster iteration than manual video creation because generation is automated from text prompts
image-to-video synthesis from static images
Generates videos from static image inputs using MiniMax's image-to-video API, exposed via MCP @mcp.tool decorator. The server accepts an image file (PNG, JPEG, or other formats), optionally a text prompt for motion guidance, sends them to MiniMax's image-to-video endpoint, and returns either a URL or local file path to the generated video. Handles image encoding, region-specific API routing, and asynchronous video generation with completion status handling.
Unique: Integrates MiniMax's image-to-video as an MCP tool with dual resource modes and optional motion prompts, enabling video animation from static images within Claude Desktop/Cursor without external video software
vs alternatives: More accessible than building custom animation pipelines because MCP handles image encoding and API communication; faster than manual video production because animation is generated automatically from static images
voice list enumeration and discovery
Exposes MiniMax's available voices through a list_voices MCP tool that returns a structured list of voice identifiers, names, and metadata. The server queries MiniMax's voice catalog API and caches or returns the results in real-time. This enables clients to discover available voices for text_to_audio synthesis without hardcoding voice IDs, supporting dynamic voice selection in Claude Desktop and Cursor workflows.
Unique: Provides voice discovery as an MCP tool, enabling dynamic voice selection within Claude Desktop/Cursor without hardcoding voice IDs; supports region-aware voice catalog queries
vs alternatives: More flexible than static voice lists because voice discovery is dynamic and API-driven; simpler than building custom voice metadata systems because MiniMax API provides the authoritative voice catalog
+4 more capabilities