Developer · Remote MCP server
ChromaDB Remote MCP Server
Remote ChromaDB vector database MCP server with streamable HTTP transport.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.meloncafe/chromadb-remote-mcp- Version
- 1.0.2
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Package
- OCI image (Docker)
- Published
- 2025-10-31
- Updated
- 2025-10-31
- Publisher
- meloncafe (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/meloncafe) · how
- Repository
- github.com/meloncafe/chromadb-remote-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://meloncafe.github.io/chromadb-remote-mcp/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 405)
- Handshake
- HTTP 405
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker)runtime: docker | devsaurus/chromadb-remote-mcp:latest | - | HTTP |
How to connect ChromaDB Remote MCP Server
ChromaDB Remote MCP Server is a remote MCP server: there is nothing to install. Its endpoint is https://meloncafe.github.io/chromadb-remote-mcp/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: devsaurus/chromadb-remote-mcp:latest. The package starts a local server that speaks MCP over Streamable HTTP; the client then connects to it by URL (the entry names docker as the runtime). It reads these environment variables: CHROMADB_MCP_URL (required) and MCP_AUTH_TOKEN (secret); set them in the client's configuration for this server.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| ChimeraForgeLocal-first LLM deployment planner: GPU/VRAM sizing, cost and latency, with provenance. | Local · stdio |
| ChippBuild and manage Chipp AI apps: prompts, knowledge, custom actions, and chat with your apps. | Remote · HTTPLive check: sign-in required |
| ChipzenAI poker arena for agents. Play rated poker on chipzen.ai against LLM bots and human-built bots. | Local · stdio |
| ChirpStackManage and live-debug LoRaWAN devices on a ChirpStack v4 network server over its gRPC API. | Local · stdio |
| Chrome Debugger MCPChrome breakpoint debugging MCP server for inspecting runtime values and stepping through code. | Local · stdio |
| Chromedevtoolsmcp MCPA paid remote MCP for AI agent browser DevTools MCP, built to return verdicts, receipts, usage logs,. | Remote · HTTPLive check: ✗ no handshake |
| Chromium BridgeMCP bridge between Chromium browsers (Arc, Vivaldi, Brave) and Claude Code: browser automation. | Local · stdio |
| ChronTimestamped audit log for every AI conversation - stored locally in SQLite, owned by you. | Local · stdio |