rcon-mcp-server

mjmorales/rcon-mcp-server

3.1

If you are the rightful owner of rcon-mcp-server and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to dayong@mcphub.com.

A Model Context Protocol (MCP) server that provides tools for connecting to and managing RCON (Remote Console) servers.

Tools
4
Resources
0
Prompts
0

RCON MCP Server

A Model Context Protocol (MCP) server that provides tools for connecting to and managing RCON (Remote Console) servers. This server enables AI assistants and other MCP clients to interact with game servers and other applications that support the RCON protocol.

Features

  • Multiple Simultaneous Connections: Manage multiple RCON sessions concurrently
  • Session Management: Create, list, and remove RCON sessions with friendly names
  • Secure Authentication: Password-based authentication for RCON servers
  • Command Execution: Execute commands on connected RCON servers
  • Thread-Safe Operations: All operations are thread-safe for concurrent use
  • Clean Architecture: Well-structured Go code with comprehensive tests

Installation

Quick Install (Recommended)

You can install a pre-built binary using our install script:

# Install the latest version (replace v1.0.0 with desired version)
curl -sSfL https://raw.githubusercontent.com/mjmorales/rcon-mcp-server/main/bin/install.sh | bash -s v1.0.0

Or if you prefer to review the script first:

# Download and review the script
curl -sSfL https://raw.githubusercontent.com/mjmorales/rcon-mcp-server/main/bin/install.sh -o install.sh
cat install.sh  # Review the script
bash install.sh v1.0.0

The install script will:

  • Automatically detect your OS and architecture
  • Download the appropriate pre-built binary
  • Install it to /usr/local/bin (or current directory if no write access)

Prerequisites

  • Go 1.24.5 or higher (only for building from source)
  • Git (only for building from source)

Install with go install

If you have Go installed, you can install directly from source:

go install github.com/mjmorales/rcon-mcp-server@latest

This will download, compile, and install the binary to your $GOPATH/bin directory.

Building from Source

# Clone the repository
git clone https://github.com/mjmorales/rcon-mcp-server.git
cd rcon-mcp-server

# Build the binary
go build -o rcon-mcp-server

# Or install globally
go install

Usage

Starting the Server

# Start the MCP server
./rcon-mcp-server serve

# Or if installed globally
rcon-mcp-server serve

The server will start and listen for MCP connections via stdio.

Available MCP Tools

The server provides the following tools:

  1. rcon_connect - Connect to an RCON server

    • session_id (required): Unique identifier for this session
    • name (optional): Friendly name for the connection
    • address (required): RCON server address (host:port)
    • password (required): RCON server password

  2. rcon_disconnect - Disconnect from an RCON server

    • session_id (required): Session ID to disconnect

  3. rcon_execute - Execute a command on an RCON server

    • session_id (required): Session ID to use
    • command (required): Command to execute

  4. rcon_list_sessions - List all active RCON sessions

    • No parameters required

Example Configuration

For Claude Desktop or other MCP clients, add this to your configuration:

{
  "mcpServers": {
    "rcon": {
      "command": "/path/to/rcon-mcp-server",
      "args": ["serve"]
    }
  }
}

Running as a Daemon

A useful tool to run as a daemon on OSX is https://github.com/mjmorales/daemon-control

Manually add this configuration to your daemon-control daemons.yml using daemon-control edit:

daemons:
  - name: rcon-mcp-server
    label: com.mjmorales.rcon-mcp-server
    description: RCON Model Context Protocol server
    program_arguments:
      - /path/to/rcon-mcp-server
      - serve
    working_directory: /path/to/rcon-mcp-server
    environment_variables:
      PATH: /usr/local/bin:/usr/bin:/bin
    standard_out_path: $HOME/Library/Logs/rcon-mcp-server.log
    standard_error_path: $HOME/Library/Logs/rcon-mcp-server.error.log
    run_at_load: true
    keep_alive:
      successful_exit: false
      crashed: true
    throttle_interval: 30

This configuration will:

  • Start the server automatically at system boot
  • Restart it if it crashes
  • Log output to ~/Library/Logs/
  • Use a 30-second throttle to prevent rapid restart loops

Development

Project Structure

rcon-mcp-server/
├── cmd/                    # CLI commands
│   ├── root.go            # Root command setup
│   └── serve.go           # Serve command implementation
├── internal/              # Internal packages
│   ├── mcp/              # MCP server implementation
│   │   └── server.go     # MCP tool handlers
│   └── rcon/             # RCON protocol implementation
│       ├── client.go     # RCON client
│       └── session.go    # Session management
├── main.go               # Entry point
└── go.mod               # Go module definition

Running Tests

# Run all tests
go test ./... -v

# Run tests with coverage
go test ./... -v -cover

# Generate coverage report
go test ./... -coverprofile=coverage.out
go tool cover -html=coverage.out -o coverage.html

Code Quality

The codebase follows Go best practices:

  • Comprehensive documentation for all exported types and functions
  • Thread-safe operations with proper mutex usage
  • Error handling with descriptive error messages
  • Table-driven tests with good coverage
  • Clean separation of concerns

RCON Protocol

This server implements the Source RCON Protocol, which is widely supported by game servers including:

  • Minecraft
  • Counter-Strike
  • Team Fortress 2
  • Rust
  • ARK: Survival Evolved
  • And many others

Protocol Details

The RCON protocol uses TCP connections with packet-based communication:

  • Packet structure: Size (4 bytes) + ID (4 bytes) + Type (4 bytes) + Body + Null terminators
  • Authentication required before command execution
  • Request/response matching using packet IDs

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

Guidelines

  1. Follow Go conventions and best practices
  2. Add tests for new functionality
  3. Update documentation as needed
  4. Ensure all tests pass before submitting

License

This project is licensed under the MIT License - see the LICENSE file for details.

Security

  • Never commit RCON passwords or sensitive information
  • Use environment variables or secure configuration for credentials
  • Be cautious when exposing RCON access through MCP

Troubleshooting

Connection Issues

  • Ensure the RCON server is running and accessible
  • Verify the server address format is host:port
  • Check that RCON is enabled on the target server
  • Confirm the password is correct

Session Management

  • Each session requires a unique ID
  • Sessions persist until explicitly disconnected
  • Use rcon_list_sessions to see all active sessions

Support

For issues, questions, or contributions, please visit the GitHub repository.