Add the Rocket.Chat MCP server to Windsurf
Config last verified Jun 1, 2026
The exact config to run Rocket.Chat in Windsurf — paste it in, restart, and the tools load.
Prerequisites
- Windsurf 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 ~/.codeium/windsurf/mcp_config.json
On Windows the file lives at %USERPROFILE%\.codeium\windsurf\mcp_config.json.
2. Add this configuration
Add to ~/.codeium/windsurf/mcp_config.json
~/.codeium/windsurf/mcp_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 Windsurf and confirm the Rocket.Chat tools load.
Gotchas
Windsurf's Cascade reads MCP servers from an "mcpServers" object in ~/.codeium/windsurf/mcp_config.json. Unlike most clients, remote servers are configured with the "serverUrl" field rather than "url", so a config that uses "url" silently fails to connect. Native remote transport is supported without an OAuth flow.