Blender MCP vs Chroma MCP

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

	Blender MCP MCP Servers	Chroma MCP MCP Servers
Tagline	Give Claude hands inside Blender — an MCP server for natural-language 3D modeling.	Official MCP server that gives LLM clients direct access to the Chroma vector database.
Category	MCP Servers	MCP Servers
Pricing	Free· Free and open-source (MIT license). No hosted service, no subscription; you supply your own MCP-capable client (Claude Desktop, Cursor, VS Code, OpenCode) and pay only for whatever LLM the client uses.	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.
Model	Model-agnostic; commonly paired with Claude (Sonnet/Opus) via Claude Desktop, but works with any MCP-capable client	—
Editorial score	—	—
Use cases	AI-assisted 3D scene blockingGenerative prop and mesh creation via Hyper3D RodinPoly Haven HDRI and texture stagingSketchfab asset search and importMaterial and lighting iteration by chatViewport screenshot review loopsBlender Python scripting via natural languageReference-image to 3D model workflowsRapid product render setup	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
Pros	Extremely popular and actively maintained MCP server (25k+ GitHub stars) with a clear install path Real two-way integration: the LLM can inspect the scene, act, then look at a screenshot and iterate Bundled asset integrations (Poly Haven, Sketchfab, Hyper3D Rodin) let the agent pull in production-ready models and HDRIs Works with several major MCP clients (Claude Desktop, Cursor, VS Code, OpenCode), not locked to one vendor MIT-licensed and fully local — no cloud rendering, no telemetry, your .blend files never leave the machine The execute_blender_code tool is a genuine power-user escape hatch for anything the higher-level tools don't cover	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
Cons	execute_blender_code runs arbitrary Python in your Blender session, which is a real security risk if you paste in untrusted prompts Requires a manual setup dance (install add-on, edit client JSON, run uvx server) that will trip up non-technical artists Quality depends entirely on the connected LLM — small or cheap models struggle to plan multi-step scene edits Complex operations often need to be broken into small steps or they silently fail or produce garbage geometry No GUI feedback inside the client beyond screenshots — long agent runs can drift from what the artist actually wanted Sketchfab/Hyper3D asset integrations depend on third-party accounts and API keys with their own quotas and terms	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
Website	github.com	github.com

Pick Blender MCP if

✅ Extremely popular and actively maintained MCP server (25k+ GitHub stars) with a clear install path
✅ Real two-way integration: the LLM can inspect the scene, act, then look at a screenshot and iterate
✅ Bundled asset integrations (Poly Haven, Sketchfab, Hyper3D Rodin) let the agent pull in production-ready models and HDRIs
✅ Works with several major MCP clients (Claude Desktop, Cursor, VS Code, OpenCode), not locked to one vendor

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

Compare a different pair →