xbox-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TV_NAME | No | The TV, as the TV plugin knows it, configured under [tv] name in ~/.config/xbox-mcp/config.toml. | |
| TV_DEVICE | No | The device on the TV's input, as the TV plugin knows it, configured under [tv] device in ~/.config/xbox-mcp/config.toml. | |
| NIGHT_ENDS | No | The hour when the night rule ends. Configured under [night] ends in ~/.config/xbox-mcp/config.toml. | 7 |
| TV_COMMAND | No | The command used to reach the TV plugin's own tools, configured under [tv] command in ~/.config/xbox-mcp/config.toml. | |
| NIGHT_STARTS | No | The hour when the night rule starts, during which a wake needs that TV already on. Configured under [night] starts in ~/.config/xbox-mcp/config.toml. | 22 |
| LAUNCH_TITLES | No | The only games xbox_launch may start, configured under [launch] titles in ~/.config/xbox-mcp/config.toml (e.g. "Forza Horizon 5", "Minecraft"). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Says whether the owner's Xbox is on, asleep or off, and what it runs. Read each 'say' aloud as it is. Waking or sleeping it needs the owner's spoken yes: read the question aloud, and confirm only if the owner clearly says yes. At night it is not woken unless its TV is already on. No tool touches the store, purchases, the account, family, privacy, settings, friends or messages, and none switches a TV on or off.
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 |
|---|---|
| xbox_statusA | Is it on, and what runs? Whether the Xbox is on, asleep or off, and the game or app it runs. |
| xbox_power_requestA | Asks before wake or sleep. Action: wake or sleep. Sends nothing: read the question in 'say' aloud, and pass its token to xbox_power_confirm only on the owner's clear yes. At night a wake is refused unless the TV is already on. |
| xbox_power_confirmA | Carry out the owner's yes. Token: from the latest xbox_power_request, used once, within 30 seconds. Wakes or sleeps the Xbox, says 'not confirmed' until its status shows it, and after a wake switches the TV to the Xbox. |
| xbox_launchA | Start a listed game. Title: words of a game on the owner's own list. Only an installed title on that list starts, only while the Xbox is on, and the answer says 'not confirmed' until the Xbox shows it. |
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 4 tools
Each tool maps to a distinct step: status reads state, power_request asks the owner, power_confirm executes the token, and launch starts a game. The descriptions explicitly explain the request→confirm handoff, so there is no realistic misselection.
All names share the xbox_ snake_case prefix and a predictable verb/noun shape (xbox_power_request, xbox_power_confirm, xbox_launch). xbox_status is a bare noun getter rather than an action name, a minor deviation in an otherwise consistent scheme.
Four tools is small but sensible for a single-device control surface, and each earns its place. It is on the thin side, though the split of power into request/confirm justifies two entries.
Status, power lifecycle, and launching are covered, but there is no tool to list the owner's games (xbox_launch requires a title from a list the agent cannot read) and no way to quit an app or handle media/volume. These are notable gaps that could dead-end an agent.