Add the Chroma MCP server to Windsurf

Config last verified Jun 1, 2026

The exact config to run Chroma in Windsurf — paste it in, restart, and the tools load.

Prerequisites

  • Windsurf installed.

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": {
    "chroma": {
      "command": "uvx",
      "args": [
        "chroma-mcp"
      ],
      "env": {
        "CHROMA_CLIENT_TYPE": "<CHROMA_CLIENT_TYPE>",
        "CHROMA_DATA_DIR": "<CHROMA_DATA_DIR>",
        "CHROMA_TENANT": "<CHROMA_TENANT>",
        "CHROMA_DATABASE": "<CHROMA_DATABASE>",
        "CHROMA_API_KEY": "<CHROMA_API_KEY>"
      }
    }
  }
}

3. Restart Windsurf and confirm the Chroma 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.

← Back to the Chroma MCP server