mister-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TV_NAME | No | The TV, as tv-mcp knows it (e.g., "the den"). Set in ~/.config/mister-mcp/config.toml under [tv] name. | |
| SIMULATE | No | Run in simulation mode without a MiSTer (`--simulate`). Answers from a pretend MiSTer. | false |
| TV_DEVICE | No | The device on its input, as tv-mcp's settings name it (e.g., "MiSTer"). Set in ~/.config/mister-mcp/config.toml under [tv] device. | |
| TV_COMMAND | No | The command to start the TV plugin server, as a JSON array of strings, e.g. ["uv", "run", "--directory", "~/tv-mcp", "tv-mcp", "serve"]. Set in ~/.config/mister-mcp/config.toml under [tv] command. | |
| MISTER_ADDRESS | No | The MiSTer on the home network (e.g., "192.0.2.10"). Set in ~/.config/mister-mcp/config.toml under [mister] address. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
A SIMULATED MiSTer, not a real one: say so. Says what the owner's MiSTer FPGA is playing and finds its games by name. Read each 'say' aloud as it is. Start a game only when the owner asks for it now. When a game is running, mister_launch asks first: read its question, and call mister_launch_confirm with its token only if the owner clearly says yes. update_all is the same: mister_update_request asks, and only the owner's clear yes goes to mister_update_confirm; mister_update_status says how it is going. Only update_all changes files on the MiSTer, and no tool switches a TV on.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mister_statusA | What is it playing? Whether the MiSTer is on, and the system and game it runs. |
| mister_searchB | Find a game by its name. Name: words from the game's title, as the owner said them. |
| mister_launchB | Start a game or a core. Game: words of its title. System: its name, alone to start its core with no game. Then the TV it is plugged into shows it, only if that TV is already on. |
| mister_launch_confirmA | Say yes to a start. Only after the owner clearly said yes to the question mister_launch asked. Token: the one that question gave. |
| mister_update_requestA | Update the MiSTer with update_all. Asks first and starts nothing: checks the free space and names a running game. Read its question aloud. |
| mister_update_confirmA | Go ahead with update_all. Only after the owner clearly said yes to the question mister_update_request asked. Token: the one that question gave. |
| mister_update_statusA | How is the update going? Whether update_all runs, its current step, and how it ended. |
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 7 tools
Each tool targets a distinct action+resource: status (playback state), search (find game), launch/launch_confirm (start with token gating), update_request/update_confirm/update_status (update lifecycle). The token-based confirm tools are explicitly tied to their request counterparts, and mister_status vs mister_update_status are clearly separated by 'playing' vs 'update progress'.
All tools share the mister_ prefix and snake_case, with the update_* family (request/confirm/status) and launch/launch_confirm forming a predictable request-confirm pattern. Minor inconsistency in that some names are bare actions (status, search) while others are compound, but overall readable and coherent.
Seven tools is well-scoped for controlling a MiSTer device: query, search, launch flow, and update flow. Each tool earns its place, and the split of launch/update into request+confirm+status is justified by the safety-confirmation design.
Core workflows (status, search, launch, update with confirmation and progress) are well covered. However, there is no explicit way to stop a running game or power off the device, which are notable gaps for a gaming-device controller, though launching a bare core may work around stopping.