Chroma MCP vs Home Assistant MCP

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	Chroma MCP MCP Servers	Home Assistant MCP MCP Servers
Tagline	Official MCP server that gives LLM clients direct access to the Chroma vector database.	Open-source MCP server that lets any LLM control and observe a Home Assistant smart home in real time.
Category	MCP Servers	MCP Servers
Pricing	Free· Open source (Apache 2.0). Free to run locally or self-hosted; embedding-function API keys (OpenAI, Cohere, Jina, VoyageAI, Roboflow) billed by those providers. Chroma Cloud pricing set separately by Chroma.	Free· Free and open source (Apache 2.0). Self-hosted; only cost is your own Home Assistant instance and the LLM client you connect to it.
Model	—	—
Editorial score	—	—
Use cases	Long-term memory for Claude DesktopTeam knowledge base shared across agentsRAG over local documentsSemantic code search in Cursor or ContinueVector store for custom MCP agentsPersonal notes and journal recallMetadata-filtered document retrievalChroma Cloud access from LLM clients	Conversational smart-home control from Claude Desktop or CursorLLM-driven Home Assistant automationsReal-time device state monitoring via SSEVoice-agent frontends that call HA servicesBulk add-on and HACS package management through chatPrototyping custom home-lab AI assistantsNatural-language climate and lighting scenesCamera snapshot and motion event triaging
Pros	Official server from the Chroma team, tracks the database's features closely Four deployment modes (ephemeral, persistent, HTTP, Chroma Cloud) from one binary Twelve well-scoped MCP tools cover the full collection and document lifecycle Supports six embedding functions including OpenAI, Cohere, Jina, and VoyageAI with per-collection persistence Zero-config install via uvx - drops into Claude Desktop or Cursor in a couple of JSON lines Apache 2.0 licensed and readable Python source; easy to fork or extend Query tools expose HNSW tuning and metadata/full-text filters, not just naive semantic search	Broad domain coverage — lights, climate, covers, media, locks, vacuums, cameras, and more mapped to MCP tools out of the box Real-time SSE subscriptions let an LLM react to state changes and automation triggers, not just poll Docker Compose setup and clear env-var config make it easy to run alongside an existing Home Assistant install Exposes system-level surfaces most HA wrappers skip: add-on management, HACS package installs, automation CRUD Token auth plus rate limiting on the bridge, so it isn't a trivially open control plane Apache 2.0 licensed, TypeScript, 500+ GitHub stars and active commits — reasonable community traction for an MCP project
Cons	You still have to run and back up the Chroma store yourself unless you pay for Chroma Cloud Command-line API key arguments are convenient but leak into process lists; env/.env path is safer but extra setup No built-in access control or multi-tenant isolation - anything the MCP client sees, it can delete Embedding-function persistence only works for collections created on Chroma v1.0.0+; older stores need migration Python-only server; teams on pure Node stacks add a runtime dependency MCP tool surface is CRUD-shaped - no higher-level RAG primitives like chunking, re-ranking, or hybrid fusion	Requires a working Home Assistant instance and long-lived access token — not useful without one Self-hosted only; you own the reverse-proxy, TLS, and network exposure decisions Model-agnostic by design, so quality of device control depends heavily on which LLM client you attach Single-maintainer community project — issue triage and roadmap can be slower than vendor MCP servers Broad tool surface can flood an LLM's context window if you don't scope subscriptions to specific domains
Website	github.com	github.com

Pick Chroma MCP if

✅ Official server from the Chroma team, tracks the database's features closely
✅ Four deployment modes (ephemeral, persistent, HTTP, Chroma Cloud) from one binary
✅ Twelve well-scoped MCP tools cover the full collection and document lifecycle
✅ Supports six embedding functions including OpenAI, Cohere, Jina, and VoyageAI with per-collection persistence

Pick Home Assistant MCP if

✅ Broad domain coverage — lights, climate, covers, media, locks, vacuums, cameras, and more mapped to MCP tools out of the box
✅ Real-time SSE subscriptions let an LLM react to state changes and automation triggers, not just poll
✅ Docker Compose setup and clear env-var config make it easy to run alongside an existing Home Assistant install
✅ Exposes system-level surfaces most HA wrappers skip: add-on management, HACS package installs, automation CRUD

Compare a different pair →