Add the Rocket.Chat MCP server to Claude Desktop

Config last verified Jun 1, 2026

The exact config to run Rocket.Chat in Claude Desktop — paste it in, restart, and the tools load.

Prerequisites

Claude Desktop installed.
ROCKETCHAT_URL — Base URL of your Rocket.Chat server. Required.
ROCKETCHAT_AUTH_TOKEN — Rocket.Chat personal access token. Required.
ROCKETCHAT_USER_ID — Rocket.Chat user ID that owns the token. Required.

Setup

1. Open `~/Library/Application Support/Claude/claude_desktop_config.json`

On Windows the file lives at %APPDATA%\Claude\claude_desktop_config.json.

2. Add this configuration

Add to ~/Library/Application Support/Claude/claude_desktop_config.json

~/Library/Application Support/Claude/claude_desktop_config.json

json

{
  "mcpServers": {
    "rocketchat": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "ROCKETCHAT_URL",
        "-e",
        "ROCKETCHAT_AUTH_TOKEN",
        "-e",
        "ROCKETCHAT_USER_ID",
        "ghcr.io/enyonee/rocketchat-mcp:latest"
      ],
      "env": {
        "ROCKETCHAT_URL": "<ROCKETCHAT_URL>",
        "ROCKETCHAT_AUTH_TOKEN": "<ROCKETCHAT_AUTH_TOKEN>",
        "ROCKETCHAT_USER_ID": "<ROCKETCHAT_USER_ID>"
      }
    }
  }
}

3. Restart Claude Desktop and confirm the Rocket.Chat tools load.

Gotchas

Claude Desktop reads MCP servers from an "mcpServers" object, but the config file is stdio-only: it cannot dial a remote URL directly. To reach a remote server you bridge it locally by running "npx mcp-remote <url>" as the command. Native remote Connectors exist on paid plans, but not through this config file, so the bridge is the portable path.

← Back to the Rocket.Chat MCP server