Chroma MCP Server

Created By
privetina year ago
A Model Context Protocol (MCP) server implementation that provides vector database capabilities through Chroma.
Overview

what is Chroma MCP Server?

Chroma MCP Server is a Model Context Protocol (MCP) server implementation that provides vector database capabilities through Chroma, enabling semantic document search, metadata filtering, and document management with persistent storage.

how to use Chroma MCP Server?

To use Chroma MCP Server, start the server using the command uv run chroma and interact with it using MCP tools to create, read, update, and delete documents or to perform semantic searches.

key features of Chroma MCP Server?

  • Semantic Search: Find documents based on meaning using Chroma's embeddings.
  • Metadata Filtering: Filter search results by metadata fields.
  • Content Filtering: Additional filtering based on document content.
  • Persistent Storage: Data persists in local directory between server restarts.
  • Comprehensive Error Handling: Clear messages for common errors.
  • Automatic Retry Logic: For transient failures.

use cases of Chroma MCP Server?

  1. Managing academic papers and research documents.
  2. Implementing a semantic search engine for document retrieval.
  3. Storing and filtering documents based on metadata for various applications.

FAQ from Chroma MCP Server?

  • What programming language is required to run Chroma MCP Server?

Python 3.8+ is required to run the server.

  • Can I use Chroma MCP Server for large datasets?

Yes, it is designed to handle document storage and retrieval efficiently.

  • Is there a way to test the server's functionality?

Yes, you can use the MCP Inspector for interactive testing of CRUD operations and search functionality.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
privetin
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago