Xbox AI Controller MCP Server

Overview Schema Source Related Servers Discussions Admin

xbox_button

Sends virtual Xbox controller button presses—A, B, X, Y, D-pad, Guide, View, or Menu—to a target console over Wi-Fi for remote navigation and control.

Instructions

Sends controller buttons to the console: 'a', 'b', 'x', 'y', 'up', 'down', 'left', 'right', 'nexus' (Guide button), 'view' (Back), 'menu' (Start).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "button": "<button>"
    },
    "name": "xbox_button"
  }
}

Input Schema

Name	Required	Description	Default
`ip`	No	Target IP address (optional if saved in config).
`button`	Yes	Button to press: 'a', 'b', 'x', 'y', 'up', 'down', 'left', 'right', 'nexus', 'view', 'menu'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 24, 2026

TDQS

A3.8/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden. It states that buttons are sent to the console but does not disclose whether authentication/reachability is required, whether presses are one-shot or repeatable, what side effects may occur, or what errors look like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no wasted text. The button list is compact and directly useful for invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter remote-control command with full schema coverage and no output schema, the description provides enough to call the tool correctly. It omits deeper behavioral context, but the core action and accepted button values are complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents both parameters. The description adds meaningful semantic mapping for special buttons like nexus (Guide), view (Back), and menu (Start), which goes beyond the raw enum-like values in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Sends controller buttons to the console.' It also enumerates the supported buttons, so an agent can distinguish this remote-input tool from siblings like xbox_launch, xbox_media, or xbox_power_on.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the remote-control framing and button list, but the description does not explicitly say when to use this tool versus siblings such as xbox_launch or xbox_media. It gives enough context to infer navigation/UI input, but no exclusions or alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server