sigma-streaming-platform-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIGMA_TOKEN | Yes | Personal API Token (pat_...) | |
| SIGMA_BASE_URL | Yes | Traefik ingress URL (e.g. https://api.sigma.example.com) |
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 |
|---|---|
| list_appsA | List all tenant apps/workspaces. Use the returned id field (UUID) as appUuid for subsequent operations. The slug field is human-readable only. |
| get_app_detailA | Get detail of a specific tenant app by UUID id. |
| list_serversB | List media servers (transcoders) for a given app UUID. |
| get_server_infoB | Get detailed info for a specific server including config and current state. appUuid must be the app UUID. |
| list_channelsA | List live transcoding channels for an app UUID. Supports filtering by status and name. |
| get_channel_detailA | Get full detail of a single transcoding channel including config, inputs, targets, jobs. appUuid must be the app UUID. |
| list_error_channelsA | List all channels currently in error state for an app UUID. Quick debugging overview. |
| check_health_summaryA | Get a health overview for an app UUID: total channels and count by status (live, error, stop, etc.). |
| start_channelC | Start a stopped transcoding channel. appUuid must be the app UUID. |
| stop_channelC | Stop a transcoding channel. appUuid must be the app UUID. |
| restart_channelA | Restart a channel (stop + start). Best for error recovery. appUuid must be the app UUID. |
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 11 tools
Each tool has a clear, distinct purpose. List tools differentiate by resource (apps, channels, servers, error channels) and get tools provide details. Control verbs (start, stop, restart) are unambiguous. No overlapping functionality.
All tools follow a consistent verb_noun pattern with snake_case (list_apps, get_channel_detail, start_channel). Verbs like list, get, start, stop, restart, and check are used uniformly.
11 tools cover the main operations for a streaming platform: listing, details, channel control, health check, and server info. This is well-scoped without unnecessary duplication.
Core lifecycle operations are present (list, get, start, stop, restart) for channels, plus health and server info. Missing creation or update tools for apps or channels, but these may be out of scope. The surface is mostly complete for management tasks.