Tencent START MCP. Automate game session and worker management.

Tencent START MCP Server gives your AI agent direct command over cloud gaming operations for Tencent START Cloud Gaming. You'll manage entire game server sessions and orchestrate resource scaling without writing a single line of boilerplate API code. It handles everything from initial user connection to shutting down resources when the action is done.

Managing Game Sessions

You can initiate a new gaming session for any user using create_session. When a player is done, call stop_game to end the active instance and release its worker resource back into the pool. If you only need to cut the video feed without killing the whole game process, use stop_publish_stream or stop_publish_stream_by_action to stop the stream by specific action code.

Monitoring Infrastructure Status

To understand what's running, start with list_games, which gives you a rundown of every game title currently available on the Tencent GS platform. You can then check usage metrics: call get_concurrent_user_info to retrieve the current number of active users connected to a specific game ID. To see how close you are to hitting your limits, use get_capacity_limit, which checks the maximum allowed concurrent users for that same game ID.

For deeper status checks, list_workers gives you a full inventory and operational status of every cloud gaming worker instance out there. If you need details on one specific user's machine, get_worker_info fetches detailed status information using the associated user ID.

Scaling and Resource Control

When player demand spikes, you don't want your service to crash. You can adjust the maximum number of simultaneous users for any game title by calling modify_capacity_limit, which updates that hard cap when scaling is necessary. Before a user connects, it’s smart to reserve their spot; use try_lock_worker to attempt reserving a worker instance for a specific user, keeping it locked down so no other process allocates it elsewhere.

If you need to know what games are even available before running any checks, start with list_games.

Operational Flow

You can execute complex operational sequences through this single server connection. You'll first use list_games to identify the target title, then check current usage via get_concurrent_user_info, and verify the hard limit with get_capacity_limit. If you determine scaling is required, call modify_capacity_limit. Once capacity is set and workers are available (which you monitor using list_workers), you can execute a session start with create_session or pre-reserve resources by calling try_lock_worker for mission-critical users.

When the user connects, their dedicated worker status comes through via get_worker_info. To ensure clean shutdown, you'll use stop_game, and if needed, follow up with a stream stop using either stop_publish_stream or stop_publish_stream_by_action to guarantee the video feed terminates cleanly. You won't need to write custom logic for these transitions; this server handles it all.