Tomo Streaming MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOMO_STREAM_URL | Yes | The control-plane URL for the Tomo Streaming server | |
| TOMO_STREAM_API_KEY | Yes | API key for authenticating with the Tomo Streaming control plane |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tomo_healthA | Check whether the Tomo Streaming control plane is reachable. |
| tomo_list_stream_serversA | List the stream-server experiences available on this control plane. |
| tomo_list_roomsA | List the authenticated client's streaming rooms and their live status. |
| tomo_create_roomA | Create a streaming room for an experience such as camera, desktop or a plugin. |
| tomo_get_roomA | Read one room's status, connected peer count and browser connection details. |
| tomo_control_roomA | Pause, resume or restart a streaming room. |
| tomo_delete_roomC | Stop and remove a streaming room after confirming the room ID. |
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 on a specific resource: health (control plane), list stream servers, CRUD for rooms plus a control action. There is no overlap between the room operations (create, list, get, control, delete) and the other tools are clearly separate.
All tool names follow a consistent `tomo_<verb>_<noun>` pattern with clear English verbs (health, list, create, get, control, delete) and nouns (stream_servers, rooms, room). The pattern is predictable and uniform.
With 7 tools, the server covers health check, resource listing, and full CRUD plus a control operation on rooms—a well-scoped set that fits its purpose without bloat or deficiency.
The tool surface provides health monitoring, stream server enumeration, and the complete lifecycle for rooms: create, read (list and get), update (control), and delete. There are no obvious gaps for the domain of managing streaming rooms.