Mirai MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MIRAI_API_KEY | No | API key for paid calls to the Mirai API. Guest quota works without a key. |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| call_modelA | Send a chat completion to Mirai and return the assistant text. Use this only to generate a reply. Do not use this to look up prices or remaining quota; use list_models or account_status. Works without MIRAI_API_KEY while daily guest quota remains. With a key, uses the paid chat completions API. |
| list_modelsA | Read the live Mirai catalog and public USD price per million tokens. Use this before choosing a model. Does not send a chat. No API key required. |
| account_statusA | Read remaining guest quota when MIRAI_API_KEY is unset, or paid balance and subscription windows when a key is set. Does not send a chat. Use list_models for prices. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| mirai-overview | Affordable model backend for the agents you already run |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: account_status for quota/balance, call_model for sending chat completions, and list_models for model catalog and prices. There is no overlap or ambiguity.
Two tools use a verb_noun pattern (call_model, list_models) while account_status is noun_noun, creating a minor inconsistency. However, all names are clear and follow a consistent lowercase snake_case style.
With only 3 tools, the set is on the low end of the typical range, but each tool serves a necessary function for the Mirai API. It is well-scoped and not overloaded.
The tool surface covers the core operations: checking account status, sending chat completions, and listing models. There are no obvious gaps, though advanced features like streaming or conversation management are absent.