rconLABSCO SUMMARY
Server admin without the console syntax.
The workshop tools are the part worth having: finding, hosting and switching to a map by ID is fiddly to type and easy to ask for. The generic rcon tool means anything else the server accepts is still reachable — including commands you would not want issued unprompted.
What it is
An RCON connection to a Counter-Strike 2 game server: arbitrary RCON commands, server status, and the workshop map handling that otherwise means typing console commands by hand.
What you get
- Any RCON command executed against the server
- Current server status read back
- The workshop maps present on the server
- A workshop map hosted by its ID
- The level changed to a given workshop map
Requirements
Docker, plus three values for the server you are controlling — its host, its RCON port and the RCON password — passed on the run command or through an env file. Communication is SSE, so the container's port has to be reachable by your client.
Setup effort
Follow the published steps — docker pull ghcr.io/v9rt3x/cs2-rcon-mcp:latest
USE CASES
01
Changing the map mid-session
See what is on the server and switch to it, without anyone alt-tabbing to a console.
02
Standing up a workshop map for a match
Host the map by its workshop ID so the server is ready before people connect.
03
Checking who is on and what is running
Server status read back in the conversation, rather than through a separate admin tool.
04
Running an admin command you would otherwise type
Any RCON command the server accepts goes through, described rather than remembered.
05
Finding out what maps the server already has
The installed workshop maps, so a request for one that is not there fails before the round does.
5 tools
Listed in project docs. Your client may show a different list.
statuslist_workshop_mapshost_workshop_mapworkshop_changelevelBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
RCON_PASSWORD in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
docker pull ghcr.io/v9rt3x/cs2-rcon-mcp:latest
docker run -p 8080:8080 -e HOST=<YOUR_SERVER_IP> -e SERVER_PORT=<YOUR_SERVER_PORT> -e RCON_PASSWORD=<YOUR_RCON_PASSWORD> ghcr.io/v9rt3x/cs2-rcon-mcp:latestPoint your MCP client at the SSE endpoint http://localhost:8080/cs2server/sse (Cursor: ~/.cursor/mcp.json; VS Code Copilot: Add MCP Server -> HTTP - server-sent events)
MCP Clients
VS Code
VS CODE · JSON
{
"servers": {
"cs2-rcon-mcp": {
"url": "http://localhost:8080/cs2server/sse"
}
}
}Cursor
CURSOR · JSON
{
"mcpServers": {
"cs2server": {
"url": "http://localhost:8080/cs2server/sse"
}
}
}
