Add the Rocket.Chat MCP server to Cursor

Config last verified Jun 1, 2026

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

Prerequisites

  • Cursor 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 ~/.cursor/mcp.json

2. Add this configuration

Add to ~/.cursor/mcp.json

~/.cursor/mcp.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 Cursor and confirm the Rocket.Chat tools load.

Gotchas

Cursor keeps MCP servers under an "mcpServers" object in ~/.cursor/mcp.json for global use, and also reads a project-scoped .cursor/mcp.json so a repository can ship its own servers. Remote servers are configured with a bare "url" field and connect natively, with OAuth handled in-app when a server requires it.

← Back to the Rocket.Chat MCP server