dannguyen9x/tiktok-live-studio-mcp

git clone https://github.com/dannguyen9x/tiktok-live-studio-mcp.git && cd tiktok-live-studio-mcp
npm.cmd ci
npm.cmd run build

Usage

• •Install client config from the .mcp.json / claude-desktop / claude-code / codex examples, pointing command: node at dist/src/index.js.
• •Start TikTok LIVE Studio before running doctor or real integration checks, then npm.cmd run doctor and npm.cmd run mcp:smoke.
• •LIVE start/stop tools (studio_start_live / studio_stop_live) require literal confirm:true and verify the state afterwards.
• •Review account, audience, scene, audio, and recording state before authorizing any LIVE action.

Key features

• ✓Twelve typed MCP tools for status, scenes, sources, audio, microphone, recording, generic Stream Deck actions, and LIVE control.
• ✓Windows process, installed-version, and process-owned-port discovery with rediscovery when LIVE Studio restarts on a different port.
• ✓Idempotent mutations with action-result validation plus post-action state verification.
• ✓Cross-process mutation lock (%TEMP% tiktok-live-studio-mcp.mutation.lock) with crashed-owner PID recovery.
• ✓Structured error contract and compact JSONL evidence logs; protocol contract verified against LIVE Studio 1.33.2.

Best for

Windows streamers and automation enthusiasts who want an AI agent to control TikTok LIVE Studio scenes, sources, audio, recording, and LIVE state safely.

Caveats

• ⚠Windows 10/11 only, with Node.js 20+ and TikTok LIVE Studio installed.
• ⚠Community project, not affiliated with TikTok, ByteDance, Elgato, Anthropic, or OpenAI.
• ⚠Some generic Stream Deck actions are conditional — LIVE Studio returns -1 when the account or LIVE state does not permit them, surfaced as structured ACTION_FAILED.
• ⚠LIVE state changes are deliberately gated behind explicit confirm:true.