ChromaDB Remote MCP Server

Name: ChromaDB Remote MCP Server
Author: meloncafe

by meloncafeversion 1.0.2i★ –iComputer or cloud

Registry nameio.github.meloncafe/chromadb-remote-mcp

Install

Overview

Description from the maker (original English)

Remote ChromaDB vector database MCP server with streamable HTTP transport

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: Streamable HTTP
Category: Search & AI memory
You need to fill in: CHROMADB_MCP_URL, MCP_AUTH_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: CHROMADB_MCP_URL, MCP_AUTH_TOKEN

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
DockerDocker installed

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://meloncafe.github.io/chromadb-remote-mcp/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "chromadb-remote": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "CHROMADB_MCP_URL",
        "-e",
        "MCP_AUTH_TOKEN",
        "devsaurus/chromadb-remote-mcp:latest"
      ],
      "env": {
        "CHROMADB_MCP_URL": "your-value",
        "MCP_AUTH_TOKEN": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http chromadb-remote https://meloncafe.github.io/chromadb-remote-mcp/mcp

Or run it on your computer

claude mcp add chromadb-remote --env CHROMADB_MCP_URL=your-value --env MCP_AUTH_TOKEN=your-value -- docker run -i --rm -e CHROMADB_MCP_URL -e MCP_AUTH_TOKEN devsaurus/chromadb-remote-mcp:latest

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "chromadb-remote": {
      "url": "https://meloncafe.github.io/chromadb-remote-mcp/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "chromadb-remote": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "CHROMADB_MCP_URL",
        "-e",
        "MCP_AUTH_TOKEN",
        "devsaurus/chromadb-remote-mcp:latest"
      ],
      "env": {
        "CHROMADB_MCP_URL": "your-value",
        "MCP_AUTH_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "chromadb-remote": {
      "type": "http",
      "url": "https://meloncafe.github.io/chromadb-remote-mcp/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "chromadb-remote": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "CHROMADB_MCP_URL",
        "-e",
        "MCP_AUTH_TOKEN",
        "devsaurus/chromadb-remote-mcp:latest"
      ],
      "env": {
        "CHROMADB_MCP_URL": "your-value",
        "MCP_AUTH_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://meloncafe.github.io/chromadb-remote-mcp/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

CHROMADB_MCP_URL required env
URL of your deployed ChromaDB Remote MCP server
MCP_AUTH_TOKEN secret env
Authentication token for the MCP server (if enabled)

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account meloncafe, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Search & AI memoryi

More stars than 0% of the other 7274 servers in this category
Published to the registry more recently than 1% of the other 7274 servers in this category
Basic checks equal to or better than 100% of the other 7274 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is ChromaDB Remote MCP Server safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: CHROMADB_MCP_URL, MCP_AUTH_TOKEN

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.2) reached the registry 12 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

ChromaDB Remote MCP Server

A Streamable HTTP MCP (Model Context Protocol) server that provides remote access to ChromaDB for AI assistants like Claude. Enables semantic search and vector database operations from mobile devices and remote locations.

Note: This project uses MCP Streamable HTTP (2025-03-26 spec). SSE transport is deprecated.

한국어 문서

Cross-Platform AI Memory Server

Compatible with ALL major AI platforms:

Claude (Desktop, Mobile, Code)
Gemini (CLI, Code Assist)
Cursor, Cline, Windsurf, VS Code Copilot
and use Remote MCP with any other MCP-compatible client

Features

Remote MCP server that enables all Claude clients (Desktop, Code, Mobile) to access the same self-hosted ChromaDB instance.

Shared Memory Across Devices - All Claude clients use the same ChromaDB instance
Self-Hosted & Private - Your data stays on your infrastructure
Remote Access - Connect from anywhere via Tailscale or public internet
Complete ChromaDB Support - All CRUD operations via MCP tools
REST API Proxy - Direct ChromaDB access for Python/JavaScript
Unified Authentication - Single token protects both MCP and REST API endpoints
Easy Deployment - One-command installation with Docker

Architecture

Overview

┌──────────────────────────────┐      ┌──────────────┐

│ Claude Desktop + Mobile │ │ Claude Code │ │ (Custom Connector - synced) │ │ (CLI setup) │ └──────────────┬───────────────┘ └──────┬───────┘ │ │ │ MCP Remote Connector │ └─────────────┬───────────────┘ │ HTTPS ┌─────────▼──────────┐ │ Remote MCP │ │ Server (Node.js) │ │ │ │ • Auth Gateway │ │ • MCP Protocol │ │ • REST API Proxy │ └─────────┬──────────┘ │ ┌─────────▼──────────┐ │ ChromaDB │ │ (Vector Database) │ │ │ │ • Embeddings │ │ • Collections │ │ • Semantic Search │ └────────────────────┘

How Clients Connect:

Claude Desktop + Mobile: Set up once using custom connector in Claude Desktop, and it automatically syncs to the mobile app. Both share the same connection automatically.
Claude Code: Requires separate setup using claude mcp add CLI command.

All clients access the same self-hosted ChromaDB through this remote MCP server. Vector embeddings and semantic search results persist across all platforms.

API Endpoints

Path	Purpose	Client	Authentication
`/mcp`	MCP Protocol	Claude Desktop/Code/Mobile	✅
`/api/v2/*`	ChromaDB REST API	Python	✅
`/docs`	Swagger UI	Browser (API docs)	✅
`/openapi.json`	OpenAPI Spec	API tools	✅
`/health`	Health check	Monitoring	❌

How It Works

Claude Desktop/Mobile: Add MCP server via custom connector (syncs automatically between devices)
Claude Code: Add MCP server using claude mcp add CLI command
Remote MCP Server authenticates requests and translates MCP protocol to ChromaDB operations
ChromaDB stores and retrieves vector embeddings for semantic search
Python can also access ChromaDB directly via the proxied REST API

Benefits:

Same vector database across all clients
Desktop and mobile share connection automatically
Self-hosted and private
Persistent memory across app restarts
Single source of truth for embeddings

Quick Start

One-Command Installation

curl -fsSL https://raw.githubusercontent.com/meloncafe/chromadb-remote-mcp/release/scripts/install.sh | bash

This will:

Download docker-compose.yml and .env.example
Auto-detect Docker Compose command (docker-compose or docker compose)
Auto-generate a secure authentication token (optional)
Configure ChromaDB data storage location (Docker volume, local directory, or custom path)
Pull Docker images
Display your authentication token and connection URL

Manual Installation

Option 1: Docker (Recommended - Pre-built Image)

# Download configuration files

mkdir chromadb-remote-mcp && cd chromadb-remote-mcp curl -O https://raw.githubusercontent.com/meloncafe/chromadb-remote-mcp/release/docker-compose.yml curl -O https://raw.githubusercontent.com/meloncafe/chromadb-remote-mcp/release/.env.example

Configure environment

cp .env.example .env

Edit .env and set:

- MCP_AUTH_TOKEN (see token generation below)

- PORT (default: 8080)

- CHROMA_DATA_PATH (default: chroma-data)

Start services

docker compose up -d

or: docker-compose up -d (for older versions)

Check health

curl http://localhost:8080/health

View logs

docker compose logs -f

Option 2: Build from Source

# Clone repository

git clone https://github.com/meloncafe/chromadb-remote-mcp.git cd chromadb-remote-mcp

Configure environment

cp .env.example .env

Edit .env with your configuration

Start with docker-compose (builds image from source)

docker compose -f docker-compose.dev.yml up -d

or: docker-compose -f docker-compose.dev.yml up -d (for older versions)

Option 3: Local Development

# Clone and install

git clone https://github.com/meloncafe/chromadb-remote-mcp.git cd chromadb-remote-mcp yarn install

Configure environment

cp .env.example .env

Edit .env file

Build and run

yarn build yarn start

Generate Secure Token

For production use, generate a secure token for MCP_AUTH_TOKEN in .env:

# Method 1: Node.js (Recommended)

node -e "console.log(require('crypto').randomBytes(32).toString('base64url'))"

Method 2: OpenSSL

openssl rand -base64 32 | tr '+/' '-_' | tr -d '='

Copy the generated token and paste it into your .env file:

MCP_AUTH_TOKEN=your-generated-token-here

Server Endpoints

MCP: http://localhost:8080/mcp (via Caddy proxy)
Health: http://localhost:8080/health
ChromaDB API: http://localhost:8080/api/v2/*
Swagger UI: http://localhost:8080/docs

Configuration

Environment Variables (.env file)

All configuration is done through the .env file. Copy .env.example to .env and customize:

cp .env.example .env

Variable	Description	Default	Required
`PORT`	External port (Caddy reverse proxy)	`8080`	No
`CHROMA_DATA_PATH`	ChromaDB data storage path (volume name, `./data`, or absolute path)	`chroma-data`	No
`CHROMA_HOST`	ChromaDB host (internal)	`chromadb`	No
`CHROMA_PORT`	ChromaDB port (internal)	`8000`	No
`CHROMA_TENANT`	ChromaDB tenant	`default_tenant`	No
`CHROMA_DATABASE`	ChromaDB database	`default_database`	No
`MCP_AUTH_TOKEN`	Authentication token for MCP and REST API	-	Yes (for public access)
`CHROMA_AUTH_TOKEN`	ChromaDB auth token (if ChromaDB requires auth)	-	No
`RATE_LIMIT_MAX`	Max requests per IP per 15 minutes	`100`	No
`ALLOWED_ORIGINS`	Comma-separated list of allowed origins (DNS rebinding protection)	-	No
`CHROMA_SERVER_VERSION`	Chroma server version declared by the operator — used by `chroma_get_server_version` and `/health/detail` as the trusted version source. Warning: with the `chromadb/chroma:latest` image this value does not follow image updates and can drift — pin a version tag and set this to the same value.	`unknown` when unset; docker-compose.yml default `1.5.9`	No
`MCP_SERVER_VERSION`	MCP wrapper version — set automatically in release images (release tag → `VERSION` build-arg); no need to set it manually	`dev` when unset	No

Authentication

IMPORTANT: For public internet access (Tailscale Funnel, Cloudflare Tunnel, etc.), you must set MCP_AUTH_TOKEN in your .env file.

Generate a secure token:

# Method 1: Node.js (Recommended - from .env.example)

node -e "console.log(require('crypto').randomBytes(32).toString('base64url'))"

Method 2: OpenSSL

openssl rand -base64 32 | tr '+/' '-_' | tr -d '='

Edit your .env file:

MCP_AUTH_TOKEN=your-generated-token-here

Then restart the services:

docker compose restart

or: docker-compose restart

Supported authentication methods (v2.0.0):

`Authorization: Bearer TOKEN` — only supported way to send MCP_AUTH_TOKEN.

Recommended for service-to-service callers (API clients, scripts, MCP relays).
Compliant with MCP specification.
Example: curl -H "Authorization: Bearer YOUR_TOKEN" https://your-server.com/mcp

OAuth 2.1 / OpenID Connect — recommended for human users.

Set OIDC_ISSUERS (comma-separated issuer URLs) or OIDC_PRESET=google,github,microsoft.
Set OIDC_AUDIENCE to the resource identifier (typically your MCP server's public URL).
The server publishes RFC 9728 Protected Resource Metadata at /.well-known/oauth-protected-resource.
401 responses include WWW-Authenticate: Bearer error="...", resource_metadata="..." per RFC 6750.

Removed in v2.0.0: X-Chroma-Token header and ?apiKey= / ?token= / ?api_key= query-parameter auth are no longer accepted. Clients that previously used those paths must migrate to Authorization: Bearer. The ALLOW_QUERY_AUTH env var is ignored.

Origin Header Validation (DNS Rebinding Protection)

The server validates the Origin header for browser requests to prevent DNS rebinding attacks. This security feature is enabled by default and protects your local MCP server from malicious websites.

Default allowed origins (always permitted):

Localhost variants: localhost, 127.0.0.1, [::1]

Only the beginning is shown; read the rest in the repo

ChromaDB Remote MCP Server

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

ChromaDB Remote MCP Server

Cross-Platform AI Memory Server

Features

Architecture

Overview

API Endpoints

How It Works

Quick Start

One-Command Installation

Manual Installation

Option 1: Docker (Recommended - Pre-built Image)

Configure environment

Edit .env and set:

- MCP_AUTH_TOKEN (see token generation below)

- PORT (default: 8080)

- CHROMA_DATA_PATH (default: chroma-data)

Start services

or: docker-compose up -d (for older versions)

Check health

View logs

Option 2: Build from Source

Configure environment

Edit .env with your configuration

Start with docker-compose (builds image from source)

or: docker-compose -f docker-compose.dev.yml up -d (for older versions)

Option 3: Local Development

Configure environment

Edit .env file

Build and run

Generate Secure Token

Method 2: OpenSSL

Server Endpoints

Configuration

Environment Variables (.env file)

Authentication

Method 2: OpenSSL

or: docker-compose restart

Origin Header Validation (DNS Rebinding Protection)