Skip to main content
Chroma Package Search is the index of public code packages that powers the Package Search MCP server. It is the source of truth for which packages and versions Chroma indexes for code search and retrieval. Chroma currently indexes about 13k versions of 3k packages across multiple registries.

​
How it works

The registry is maintained in the Package Search repository. It defines what should be indexed and how to locate each package’s source at a specific version.
  • index.json declares which packages should be indexed.
  • versions.json is a generated output that lists all packages and versions currently indexed. It is automatically updated by the indexing service.
Chroma’s indexer reads these files, resolves each version to a git tag according to the package’s tag_formats, fetches the source, and indexes only files matching the package’s include globs.

​
Supported registries

Chroma supports these registries and identifiers:

​
Indexed versions

Version discovery is driven by the package’s tag formats and the underlying registry. The indexer resolves published versions to git tags (annotated or lightweight) using the configured formats. Historical indexing is bounded by the sentinel timestamp, so versions published before that time are ignored.

​
How to add a package

Anyone can request additional packages by opening a Pull Request against the Package Search repository. Follow the directions in the README to add a new package.