Ban, disconnect and disable-domain are all in the set, which is exactly what you want during a moderation incident and exactly what you do not want a model reaching for on a misread instruction. The credentials are plain Tencent Cloud API keys, so the practical control is which sub-account key you hand it — worth deciding before wiring it up rather than after.
A Python server over the Tencent Cloud Live API, so live-streaming operations can be described in plain language instead of assembled as signed API calls. The server handles signing, certificates and API version compatibility; the client just says what should happen. Coverage spans four areas: domain management, pull-to-push relay tasks, stream state, and transcoding templates.
- Domains: add, delete, enable and disable a live domain, query one domain's details, and list them all
- Pull-to-push relay: create, update, query and delete live pull tasks, for forwarding a stream to another platform
- Stream state: query which streams are currently live, and query the state of a specific stream
- Stream control: disconnect a stream, resume one, ban one, query push and disconnect events
- Delay: set a broadcast delay on a stream, or cancel it
- Transcoding: create and delete transcoding templates, and create and delete the rules that bind them
Tencent Cloud API credentials from the console: `TENCENTCLOUD_SECRET_ID` and `TENCENTCLOUD_SECRET_KEY`. The Tencent Cloud Python SDK. Run it through `uvx` from your client config after installing uv, or from source with `uv run src/server.py`. Package `tencentcloud-live-mcp-server`, version 1.1.0. The credentials are account-level, and several of the tools stop live broadcasts — scope the key accordingly.
One command plus a key — uvx tencentcloud-live-mcp-server, then supply credentials