StreamXpress MCP Server
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connectA | Connect to a StreamXpress instance running in remote-control mode. The StreamXpress must be started with: StreamXpress.exe -rc |
| disconnectA | Disconnect from the StreamXpress remote-control session. |
| scan_portsA | Scan for available output ports on the connected StreamXpress. Returns a list of port descriptors with serial, type, and output capabilities. |
| select_portB | Select a physical output port for playout. |
| open_fileC | Open a TS file for playout. |
| startA | Start TS playout on the selected port. |
| stopA | Stop TS playout. |
| get_statusA | Get current playout status including position, wraps, filename, and bitrate. |
| set_rateA | Set the TS playout bitrate in bits per second (188-byte packets). |
| set_tsoip_paramsB | Configure TS-over-IP output parameters (UDP/RTP). |
| set_rf_paramsA | Set RF output frequency and level (modulator ports only). |
| set_asi_paramsC | Set ASI output parameters. |
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 12 tools
Each tool has a clear, distinct purpose: connection management, port scanning/selection, file opening, playout start/stop, status retrieval, and parameter configuration. No two tools appear to do the same thing.
Most tools follow a clear verb_noun pattern (e.g., scan_ports, select_port, open_file, set_rate). The few single-word verbs (start, stop, connect, disconnect) are acceptable but slightly inconsistent with the underscore-separated verb_noun style.
12 tools is well within the ideal range for a device control server. Each tool covers a necessary aspect of playout control, and there is no bloat or redundancy.
The tool surface covers the core lifecycle: connect, configure port, open file, start/stop, query status, and adjust parameters. Notable gaps include lack of pause/resume or file listing, but these are not critical for the apparent primary workflow.