docs: start ChromaDB via the bundled npm CLI, drop redundant Python install#1
Open
malixsys wants to merge 1 commit into
Open
docs: start ChromaDB via the bundled npm CLI, drop redundant Python install#1malixsys wants to merge 1 commit into
malixsys wants to merge 1 commit into
Conversation
…edundant Python install The mcp-server already depends on the npm chromadb package, which ships the native chroma server CLI. Add a root 'chroma' script that runs that installed copy, and point the README and setup.js at 'npm run chroma' instead of 'pip install chromadb && chroma run', so no Python or extra download is needed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Starting ChromaDB no longer needs Python.
mcp-serveralready depends on the npmchromadbpackage, which ships the nativechromaserver CLI (with prebuilt macOS and Linux bindings). This adds a rootchromascript that runs the already-installed copy and points the docs at it.Why
The README and
setup.jstold users topip install chromadb && chroma run --path ./storage/chroma. That is redundant, the server binary is already installed via npm, and it is fragile on macOS, where a stale or broken Python/pyenv setup makespipandchromafail before anything runs. The npm route needs no Python and no second download.Changes
package.json: add"chroma": "node mcp-server/node_modules/chromadb/dist/cli.mjs run --path ./storage/chroma".README.md: drop thePython 3.10+prerequisite and thepip installblock; documentnpm run chroma.scripts/setup.js: the printed hints now point atnpm run chroma.How to test
Data persists to
./storage/chroma. Without the server, BraveMCP falls back to SQLite keyword search.