tiktok-live-studio-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TTLS_LOG_PATH | No | Path to write JSONL runtime logs. Set this to an absolute path in your MCP client configuration to override the default artifacts/evidence/runtime.jsonl. | artifacts/evidence/runtime.jsonl |
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 |
|---|---|
| studio_get_statusA | Read process, Socket.IO connection, scene, recording, and LIVE state without changing Studio. |
| studio_list_scenesA | List scenes and the active scene from verified sync_settings state. |
| studio_switch_sceneA | Idempotently switch to an exact scene and verify the resulting active scene. |
| studio_list_sourcesA | List source names, IDs, and visibility for the active or named scene. |
| studio_set_source_visibilityA | Set, verify, and preserve source visibility without a blind toggle. Restores the original scene when targeting another scene. |
| studio_set_microphone_muteA | Idempotently set and verify the aggregate LIVE Studio microphone mute state. |
| studio_set_audio_muteA | Idempotently set and verify the LIVE Studio audio output mute state. |
| studio_start_recordingA | Start local recording only when stopped, then verify recording state. |
| studio_stop_recordingA | Stop local recording only when active, then verify recording state. |
| studio_trigger_actionA | Emit one action from the verified LIVE Studio 1.33.2 Stream Deck protocol. Parameterized and stateful actions should use dedicated tools. |
| studio_start_liveB | Start LIVE only with confirm:true and only when readable state makes the toggle safe. |
| studio_stop_liveA | Stop LIVE only with confirm:true and verify the resulting offline state. |
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 targets a distinct resource and action: status, scenes, sources, audio (mic vs output), recording, live, and a generic trigger. The overlap between microphone_mute and audio_mute is clearly separated by description.
All tool names follow the consistent pattern studio_<verb>_<object>, using snake_case throughout. Verbs like get, list, switch, set, start, stop are used predictably.
12 tools is well within the ideal 3-15 range and covers the full scope of controlling a live studio without unnecessary bloat.
Core lifecycle is covered: read status, manage scenes/sources, control audio, recording, and live state. Minor gaps like scene creation or source editing exist, but the generic trigger_action and robust state verification reduce dead ends.