Schema | minimax-llm-mcp

minimax-llm-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`TRANSPORT`	No	Transport the server listens on. One of stdio or sse.	stdio
`RETRY_ON_429`	No	Whether to retry once on 429 Too Many Requests with a short back-off.	true
`MINIMAX_API_KEY`	Yes	Bearer token for the MiniMax M3 LLM API.
`REQUEST_TIMEOUT_MS`	No	Per-request timeout when calling the upstream API (in milliseconds).	300000
`MINIMAX_EMBEDDING_ENABLED`	No	Reserved for a future minimax_embed tool (out of scope in 0.1.0).	false

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
minimax_chatC	Non-streaming chat completion against MiniMax M3. Returns the assistant content plus optional usage.
minimax_completeB	Single-turn text completion against MiniMax M3. Wraps a prompt (plus optional system) into a one-message conversation and returns the assistant content.
minimax_tool_callA	M3-native tool-use passthrough. Forwards `tools` and `tool_choice` verbatim to MiniMax M3 and returns the assistant content plus any proposed tool_calls. When the upstream finishes with finish_reason 'tool_calls', the text content is a structured JSON block with the call list.
minimax_count_tokensB	Local token count for a conversation using the cl100k_base BPE encoding. Returns total, model, encoding, and a per-message breakdown. Does not make a network call.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/webski101/minimax-llm-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server