Xbox Port MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_profilesB | List supported game profiles and precisely labelled historical evidence. |
| doctorA | Report local tool availability and execution/network opt-ins. Does not install anything. |
| inspect_isoA | Read an allowed local XDVDFS ISO; return bounded entries and XBE identity, without extracting. |
| inspect_xbeB | Inspect an allowed original Xbox XBE and match its exact identity to a profile. |
| create_workspaceB | Create a new isolated workspace; no source checkout, extraction or execution occurs. |
| start_stepA | Start a fixed profile step, never arbitrary shell text. extract needs an allowed ISO input_path. Other steps: prepare, fixes, configure, compile, artwork, installer, iso, verify_iso. Prepare downloads pinned trusted sources; builds may download dependencies when enabled. External steps require XBOX_PORT_ALLOW_EXECUTION=1. Returns a job id, not a completion claim. |
| get_jobB | Get process result and at most 16 KiB of log tail. A succeeded step is not playability evidence. |
| cancel_jobA | Request cancellation of a job owned by this server session, never an arbitrary PID. |
| record_manual_observationA | Record a client-reported human observation separately from automated job evidence. Only call when the user has supplied that observation. This does not independently verify it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| port_workflow | Plan a careful, evidence-labelled port workflow for a supported title. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| profiles_resource |
TDQS
Scored across 9 tools
Each tool targets a distinct resource and action: profile listing, job lifecycle (start/get/cancel), evidence recording, environment diagnostics, ISO/XBE inspection, and workspace creation. There is no meaningful overlap between inspection, execution, and observation tools.
Eight of nine tools follow a clear snake_case verb_noun pattern (list_profiles, get_job, cancel_job, inspect_iso, create_workspace, start_step, etc.). The lone exception is 'doctor', which breaks the pattern but is a conventional and readable diagnostic name.
Nine tools is well-scoped for an Xbox porting workflow that must separate job execution, evidence collection, inspection, and environment checks. Each tool has a clear role and none appear redundant.
Core lifecycle coverage exists: profiles can be listed, jobs started/retrieved/cancelled, workspaces created, and artifacts inspected. Minor gaps include no workspace listing/deletion and no explicit job listing, but agents can likely work around these.