Restream MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RESTREAM_CLIENT_ID | Yes | Your Restream API Client ID | |
| RESTREAM_API_BASE_URL | No | The Restream API base URL | https://api.restream.io/v2 |
| RESTREAM_CLIENT_SECRET | Yes | Your Restream API Client Secret |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_user_profileB | Get the authenticated user profile information including email, display name, and account details |
| list_channelsA | List all connected streaming channels/platforms (YouTube, Twitch, Facebook, etc.) with their connection status |
| get_channelC | Get detailed information about a specific channel by ID |
| update_channel_statusC | Enable or disable a specific streaming channel |
| get_current_streamB | Get information about the current/active stream including title, status, RTMP URL, and viewer count |
| update_stream_settingsC | Update settings for the current stream such as title, description, or privacy settings |
| get_stream_analyticsC | Get analytics and statistics for streams including viewer counts, engagement metrics, and performance data |
| start_streamC | Start a new stream with optional settings |
| stop_streamB | Stop the current active stream |
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 9 tools
Each tool has a clearly distinct purpose with no ambiguity. For example, get_channel retrieves channel details, while update_channel_status enables/disables channels, and start_stream/stop_stream manage stream lifecycle. The descriptions clearly differentiate between channel operations, stream operations, analytics, and user profile.
All tools follow a consistent verb_noun pattern with snake_case throughout. Verbs like get, list, start, stop, and update are used predictably, making the tool set easy to navigate. There are no deviations in naming conventions.
With 9 tools, the server is well-scoped for managing streaming operations. Each tool earns its place by covering distinct aspects like channel management, stream control, analytics, and user info, without being overwhelming or insufficient for the domain.
The tool set provides complete CRUD/lifecycle coverage for streaming management. It includes operations for listing and getting channels, starting/stopping streams, updating settings and statuses, retrieving analytics, and accessing user profiles, with no obvious gaps that would hinder agent workflows.