StreamHub 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_platformsA | Lists all supported streaming platforms (YouTube, Twitch, Kick) and their current authentication status. |
| authenticate_platformC | Triggers authentication or sets credentials directly from chat for a platform (youtube, twitch, or kick). |
| get_templatesB | Returns available user-editable Markdown templates and their metadata. |
| preview_live_metadataA | Generates a preview of live metadata (rendered description, tags, categories) without publishing. |
| prepare_liveC | Prepares and updates live broadcast configuration across selected platforms (YouTube, Twitch, Kick). |
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 5 tools
The tools mostly target distinct actions: platform discovery, authentication, template retrieval, metadata preview, and live preparation. The only mild overlap is between preview_live_metadata and prepare_live, since both concern live broadcast metadata, but their descriptions make the preview-versus-apply distinction reasonably clear.
All names use snake_case with a leading verb, producing a predictable verb_noun structure. There are minor noun-form variations such as get_templates versus preview_live_metadata versus prepare_live, but the convention is still easy to follow.
Five tools is well-scoped for a focused streaming-configuration server, with each tool covering a distinct part of the workflow. The surface does not feel bloated or arbitrarily fragmented.
The surface covers platform listing, authentication, templates, preview, and preparation, but there are notable gaps: no tool publishes or starts a live broadcast, no tool updates editable templates, and there is no explicit way to fetch current live configuration. These gaps may force agents into dead ends for end-to-end streaming workflows.