Add the Chroma MCP server to Cursor

Config last verified Jun 1, 2026

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

Prerequisites

Cursor installed.

Setup

1. Open `~/.cursor/mcp.json`

2. Add this configuration

Add to ~/.cursor/mcp.json

~/.cursor/mcp.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 Cursor and confirm the Chroma 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 Chroma MCP server