Chroma MCP Server

uvx chroma-mcp

{
  "mcpServers": {
    "chroma-mcp": {
      "command": "uvx",
      "args": [
        "chroma-mcp"
      ]
    }
  }
}

Chroma's own MCP server covers the full collection lifecycle: create, list, inspect, peek, modify and delete, plus adding, updating, querying and removing documents. The same server works against an in-memory instance, a local persistent directory, a self-hosted HTTP deployment or Chroma Cloud, selected with a client-type flag. That range makes it convenient for prototyping a retrieval setup locally and pointing the identical configuration at a hosted database later. Credentials are only needed for the cloud and HTTP modes.