Add the Rocket.Chat MCP server to VS Code

Config last verified Jun 1, 2026

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

Prerequisites

  • VS Code 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 .vscode/mcp.json

2. Add this configuration

Add to .vscode/mcp.json

.vscode/mcp.json
json
{
  "servers": {
    "rocketchat": {
      "type": "stdio",
      "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>"
      }
    }
  }
}

Heads up

  • VS Code uses the `servers` key (not `mcpServers`) and requires `type`.

3. Restart VS Code and confirm the Rocket.Chat tools load.

Gotchas

  • VS Code uses the `servers` key (not `mcpServers`) and requires `type`.

VS Code is the exception to every other client: its top-level key is "servers", not "mcpServers", and each entry needs an explicit "type" (for example "http" or "stdio"). Secrets are not inlined; instead you declare an "inputs" array and reference each value as ${input:id}, so VS Code prompts for it once and never writes it to disk. Remote servers connect natively with OAuth.

← Back to the Rocket.Chat MCP server