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 |
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dannguyen9x/tiktok-live-studio-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server