AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
MCP verified Apache-2.0 Self-run

Chroma Mcp Custom

mcp-bryankthompson-chroma-mcp-custom · by bryankthompson

This is an enhanced fork of the original chroma-core/chroma-mcp project, featuring FastMCP architecture, streamable HTTP transport, and additional enhancements for production use.

No reviews yet
0 installs
32 views
0.0% view→install

Install

$ agentstack add mcp-bryankthompson-chroma-mcp-custom

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets Used
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/mcp-bryankthompson-chroma-mcp-custom)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
9mo ago

Declared compatibility

Claude CodeClaude DesktopCursorWindsurf

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Chroma Mcp Custom? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Chroma - the open-source embedding database. The fastest way to build Python or JavaScript LLM apps with memory!

|

|

Docs |

Homepage

Chroma MCP Server

> Note: This is an enhanced fork of the original chroma-core/chroma-mcp project, featuring FastMCP architecture, streamable HTTP transport, and additional enhancements for production use.

[](https://smithery.ai/server/@chroma-core/chroma-mcp)

MCP SDK Version

Current Version: Python MCP SDK 1.15.0 (upgraded October 1, 2025)

This server uses the latest Model Context Protocol SDK with enhanced capabilities:

New Features:

  • Paginated List Decorators: Support for paginated prompts, resources, and tools
  • Protected Resource Metadata: Improved metadata handling for resources
  • Enhanced Security: HTTP 403 responses for invalid Origin headers
  • Default Values: Elicitation schema support for default values
  • Extended Metadata: Additional metadata and icon support in SDK

Previous Version: 1.2.1 → Upgrade Jump: 13+ major versions (significant protocol enhancements)

Compatibility: The upgrade maintains full backward compatibility while enabling new optional features when MCP clients support them. All existing tool definitions and workflows continue to work unchanged.

Installation Notes:

All 123 packages installed successfully in a fresh uv virtual environment. Server tested and operational with the chroma-mcp entry point.

For complete MCP protocol documentation, see Model Context Protocol.

The Model Context Protocol (MCP) is an open protocol designed for effortless integration between LLM applications and external data sources or tools, offering a standardized framework to seamlessly provide LLMs with the context they require.

This server provides data retrieval capabilities powered by Chroma, enabling AI models to create collections over generated data and user inputs, and retrieve that data using vector search, full text search, metadata filtering, and more.

Enhancements in This Fork

> 📋 Validation: All claims below are verified with code references and evidence. See [VALIDATION.md](VALIDATION.md) for detailed verification.

Sequential Thinking Capabilities ⭐

This fork restores the Sequential Thinking feature (removed in upstream v0.2.0) and enhances it with new capabilities:

What's New:

  • Branching Support: Explore alternative solution paths from any thought in a session
  • Revision Tracking: Revise previous thoughts based on new insights while maintaining history
  • Session Management: Track complete thought chains with metadata-based organization
  • Enhanced Search: Find similar reasoning sessions using ChromaDB's vector similarity

Implementation:

  • Self-contained ChromaDB implementation using dedicated "sequential_thinking" collection
  • Metadata-driven architecture (sessionid, thoughtnumber, branch_id, revision flags)
  • No external service dependencies - works with any Chroma deployment

Use Cases: Algorithm design, code review, exploratory analysis, complex problem-solving

Verification:

  • Code: src/chroma_mcp/server.py:1054-1119 (5 sequential thinking tools)
  • Tests: tests/unit/test_sequential_thinking.py
  • Examples: examples/sequential_thinking_example.py (727 lines, 2 complete workflows)
  • Evidence: See [VALIDATION.md](VALIDATION.md) for detailed feature verification

Infrastructure Enhancements

  • FastMCP Architecture: Modernized codebase following FastMCP template patterns
  • Streamable HTTP Transport: MCP-compliant HTTP server implementation (port 10550)
  • Improved Type Safety: Full Pydantic validation and structured error handling
  • Docker-First Deployment: Production-ready containerized setup with integrated services
  • Enhanced Documentation: Comprehensive guides for development and deployment

Features

  • Flexible Client Types
  • Ephemeral (in-memory) for testing and development
  • Persistent for file-based storage
  • HTTP client for self-hosted Chroma instances
  • Cloud client for Chroma Cloud integration (automatically connects to api.trychroma.com)
  • Collection Management
  • Create, modify, and delete collections
  • List all collections with pagination support
  • Get collection information and statistics
  • Configure HNSW parameters for optimized vector search
  • Select embedding functions when creating collections
  • Document Operations
  • Add documents with optional metadata and custom IDs
  • Query documents using semantic search
  • Advanced filtering using metadata and document content
  • Retrieve documents by IDs or filters
  • Full text search capabilities
  • Sequential Thinking & Reasoning
  • Multi-step problem solving with structured thought chains
  • Thought revision and branching for exploring alternative approaches
  • Session management with complete history tracking via ChromaDB metadata
  • Find similar reasoning sessions using vector similarity search
  • Self-contained implementation - no external service dependencies

Supported Tools

  • chroma_list_collections - List all collections with pagination support
  • chroma_create_collection - Create a new collection with optional HNSW configuration
  • chroma_peek_collection - View a sample of documents in a collection
  • chroma_get_collection_info - Get detailed information about a collection
  • chroma_get_collection_count - Get the number of documents in a collection
  • chroma_modify_collection - Update a collection's name or metadata
  • chroma_delete_collection - Delete a collection
  • chroma_add_documents - Add documents with optional metadata and custom IDs
  • chroma_query_documents - Query documents using semantic search with advanced filtering
  • chroma_get_documents - Retrieve documents by IDs or filters with pagination
  • chroma_update_documents - Update existing documents' content, metadata, or embeddings
  • chroma_delete_documents - Delete specific documents from a collection

Sequential Thinking Tools

> Note: These tools enable advanced reasoning capabilities unique to this fork. The Sequential Thinking feature was removed in upstream v0.2.0 but has been restored and enhanced here. See [VALIDATION.md](VALIDATION.md#sequential-thinking-tools-validation) for verification.

  • chroma_sequential_thinking - Store and process sequential thoughts with support for:
  • Step-by-step reasoning with thought numbering
  • Thought revision (revise previous thoughts based on new insights)
  • Thought branching (explore alternative solution paths)
  • Session summarization and key thought identification
  • chroma_get_similar_sessions - Find related thinking sessions based on:
  • Content similarity (semantic search across session summaries)
  • Metadata filters (session type, thought count ranges)
  • Configurable result limits
  • chroma_get_thought_history - Retrieve complete thought chains including:
  • All thoughts in chronological order
  • Branch exploration with branch IDs
  • Revision history tracking
  • chroma_get_thought_branches - View branching thought processes:
  • Identify all branches from a specific thought
  • Track alternative solution paths
  • Navigate complex reasoning trees
  • chroma_continue_thought_chain - Analyze and continue reasoning:
  • Analyze last thought in a session
  • Provide continuation suggestions
  • Support completion, continuation, and branching analysis types

Example Use Cases: See examples/sequential_thinking_example.py for detailed demonstrations of algorithm design and code review workflows using these tools.

Embedding Functions

Chroma MCP supports several embedding functions: default, cohere, openai, jina, voyageai, and roboflow.

The embedding functions utilize Chroma's collection configuration, which persists the selected embedding function of a collection for retrieval. Once a collection is created using the collection configuration, on retrieval for future queries and inserts, the same embedding function will be used, without needing to specify the embedding function again. Embedding function persistance was added in v1.0.0 of Chroma, so if you created a collection using version APIKEY="". So to set a Cohere API key, set the environment variable CHROMACOHEREAPIKEY="". We recommend adding this to a .env file somewhere and using the CHROMADOTENV_PATH environment variable or --dotenv-path` flag to set that location for safekeeping.

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.