使用说明
MiniMax MCP JS
JavaScript/TypeScript implementation of MiniMax MCP, providing image generation, video generation, text-to-speech, and more.
Documentation
- 中文文档
- Python Version - Official Python implementation of MiniMax MCP
Release Notes
July 22, 2025
🔧 Fixes & Improvements
- TTS Tool Fixes: Fixed parameter handling for
languageBoostandsubtitleEnablein thetext_to_audiotool - API Response Enhancement: TTS API can return both audio file and subtitle file, providing a more complete speech-to-text experience
July 7, 2025
🆕 What's New
- Voice Design: New
voice_designtool - create custom voices from descriptive prompts with preview audio - Video Enhancement: Added
MiniMax-Hailuo-02model with ultra-clear quality and duration/resolution controls
📈 Enhanced Tools
voice_design- Generate personalized voices from text descriptionsgenerate_video- Now supports MiniMax-Hailuo-02 with 6s/10s duration and 768P/1080P resolution options
Features
- Text-to-Speech (TTS)
- Image Generation
- Video Generation
- Voice Cloning
- Voice Design
- Dynamic configuration (supports both environment variables and request parameters)
- Compatible with MCP platform hosting (ModelScope and other MCP platforms)
Installation
Installing via Smithery
To install MiniMax MCP JS for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @MiniMax-AI/MiniMax-MCP-JS --client claude
Installing manually
# Install with pnpm (recommended)
pnpm add minimax-mcp-js
Quick Start
MiniMax MCP JS implements the Model Context Protocol (MCP) specification and can be used as a server to interact with MCP-compatible clients (such as Claude AI).
Quickstart with MCP Client
- Get your API key from MiniMax International Platform.
- Make sure that you already installed Node.js and npm
- Important: API HOST&KEY are different in different region, they must match, otherwise you will receive an
Invalid API keyerror.
| Region | Global | Mainland |
|---|---|---|
| MINIMAX_API_KEY | go get from MiniMax Global | go get from MiniMax |
| MINIMAX_API_HOST | https://api.minimaxi.chat (note the extra "i") | https://api.minimax.chat |
Using with MCP Clients (Recommended)
Configure your MCP client:
Claude Desktop
Go to Claude > Settings > Developer > Edit Config > claude_desktop_config.json to include:
{
"mcpServers": {
"minimax-mcp-js": {
"command": "npx",
"args": [
"-y",
"minimax-mcp-js"
],
"env": {
"MINIMAX_API_HOST": "<https://api.minimaxi.chat|https://api.minimax.chat>",
"MINIMAX_API_KEY": "<your-api-key-here>",
"MINIMAX_MCP_BASE_PATH": "<local-output-dir-path, such as /User/xxx/Desktop>",
"MINIMAX_RESOURCE_MODE": "<optional, [url|local], url is default, audio/image/video are downloaded locally or provided in URL format>"
}
}
}
}
Cursor
Go to Cursor → Preferences → Cursor Settings → MCP → Add new global MCP Server to add the above config.
⚠️ Note: If you encounter a "No tools found" error when using MiniMax MCP JS with Cursor, please update your Cursor to the latest version. For more information, see this discussion thread.
That's it. Your MCP client can now interact with MiniMax through these tools.
For local development:
When developing locally, you can use npm link to test your changes:
# In your project directory
npm link
Then configure Claude Desktop or Cursor to use npx as shown above. This will automatically use your linked version.
⚠️ Note: The API key needs to match the host address. Different hosts are used for global and mainland China versions:
- Global Host:
https://api.minimaxi.chat(note the extra "i") - Mainland China Host:
https://api.minimaxi.chat
Transport Modes
MiniMax MCP JS supports three transport modes:
| Feature | stdio (default) | REST | SSE |
|---|---|---|---|
| Environment | Local only | Local or cloud deployment | Local or cloud deployment |
| Communication | Via standard I/O |
Via HTTP requests |
Via server-sent events |
| Use Cases | Local MCP client integration | API services, cross-language calls | Applications requiring server push |
| Input Restrictions | Supports local files or URL resources |
When deployed in cloud, URL input recommended |
When deployed in cloud, URL input recommended |
Configuration
MiniMax-MCP-JS provides multiple flexible configuration methods to adapt to different use cases. The configuration priority from highest to lowest is as follows:
1. Request Parameter Configuration (Highest Priority)
In platform hosting environments (like ModelScope or other MCP platforms), you can provide an independent configuration for each request via the meta.auth object in the request parameters:
{
"params": {
"meta": {
"auth": {
"api_key": "your_api_key_here",
"api_host": "<https://api.minimaxi.chat|https://api.minimaxi.chat>",
"base_path": "/path/to/output",
"resource_mode": "url"
}
}
}
}
This method enables multi-tenant usage, where each request can use different API keys and configurations.
2. API Configuration
When used as a module in other projects, you can pass configuration through the startMiniMaxMCP function:
import { startMiniMaxMCP } from 'minimax-mcp-js';
await startMiniMaxMCP({
apiKey: 'your_api_key_here',
apiHost: 'https://api.minimaxi.chat', // Global Host - https://api.minimaxi.chat, Mainland Host - https://api.minimax.chat
basePath: '/path/to/output',
resourceMode: 'url'
});
3. Command Line Arguments
- Install the CLI tool globally:
# Install globally
pnpm install -g minimax-mcp-js
- When used as a CLI tool, you can provide configuration via command line arguments:
minimax-mcp-js --api-key your_api_key_here --api-host https://api.minimaxi.chat --base-path /path/to/output --resource-mode url
4. Environment Variables (Lowest Priority)
The most basic configuration method is through environment variables:
# MiniMax API Key (required)
MINIMAX_API_KEY=your_api_key_here
# Base path for output files (optional, defaults to user's desktop)
MINIMAX_MCP_BASE_PATH=~/Desktop
# MiniMax API Host (optional, defaults to https://api.minimaxi.chat, Global Host - https://api.minimaxi.chat, Mainland Host - https://api.minimax.chat)
MINIMAX_API_HOST=https://api.minimaxi.chat
# Resource mode (optional, defaults to 'url')
# Options: 'url' (return URLs), 'local' (save files locally)
MINIMAX_RESOURCE_MODE=url
Configuration Priority
When multiple configuration methods are used, the following priority order applies (from highest to lowest):
- Request-level configuration (via
meta.authin each API request) - Command line arguments
- Environment variables
- Configuration file
- Default values
This prioritization ensures flexibility across different deployment scenarios while maintaining per-request configuration capabilities for multi-tenant environments.
Configuration Parameters
| Parameter | Description | Default Value |
|---|---|---|
| apiKey | MiniMax API Key | None (Required) |
| apiHost | MiniMax API Host | Global Host - https://api.minimaxi.chat, Mainland Host - https://api.minimax.chat |
| basePath | Base path for output files | User's desktop |
| resourceMode | Resource handling mode, 'url' or 'local' | url |
⚠️ Note: The API key needs to match the host address. Different hosts are used for global and mainland China versions:
- Global Host:
https://api.minimaxi.chat(note the extra "i") - Mainland China Host:
https://api.minimax.chat
Example usage
⚠️ Warning: Using these tools may incur costs.