minimax-coding-plan-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MINIMAX_API_KEY | Yes | Your TokenPlan API Key | |
| MINIMAX_API_HOST | No | API host, default https://api.minimaxi.com | https://api.minimaxi.com |
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 |
|---|---|
| web_searchA | You MUST use this tool whenever you need to search for real-time or external information on the web. A web search API that works just like Google Search. Args:
query (str): The search query. Aim for 3-5 keywords for best results. For time-sensitive topics, include the current date (e.g. Search Strategy: - If no useful results are returned, try rephrasing your query with different keywords. Returns: A JSON object containing the search results. |
| understand_imageA | You MUST use this tool whenever you need to analyze, describe, or extract information from an image. An LLM-powered vision tool that can analyze and interpret image content from local files or URLs based on your instructions. Only JPEG, PNG, and WebP formats are supported. Args: prompt (str): A text prompt describing what you want to analyze or extract from the image. image_source (str): The location of the image to analyze. - HTTP/HTTPS URL: "https://example.com/image.jpg" - Local file path (relative or absolute) - If path starts with @, strip the @ prefix before passing |
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 2 tools
understand_image and web_search have completely distinct purposes with no overlap. An agent would have no difficulty choosing between them.
Both tool names follow the clear verb_noun pattern (understand_image, web_search), making the naming completely consistent.
With only 2 tools, the server is on the thin side, but for a narrow utility purpose this is borderline acceptable.
The server name suggests a coding-plan focus, but the tools (image analysis and web search) do not cover that domain. There are significant gaps and no coherent lifecycle or workflow.