Chroma Package Search

Created By
Chroma9 months ago
Give coding agents the ability to understand dependencies.
Overview

Chroma Package Search is a tool that enhances coding agents by providing them with the ability to understand dependencies in code packages, improving their performance on coding tasks and reducing hallucination risks.

To use Chroma Package Search, create a Chroma account to obtain an API key, and then utilize the provided server command to access the package search functionalities.

  • package_search_grep: Executes a grep over the source code of a public package to find code using regex.
  • package_search_hybrid: Searches package source code using both semantic understanding and regex patterns for hybrid search capabilities.
  • package_search_read_file: Reads specific lines from a source file of a public package, allowing users to fetch code regions by line range.
  1. Enhancing AI coding agents with contextual understanding of code dependencies.
  2. Performing deterministic searches in code packages using regex.
  3. Fetching specific code snippets from public packages for analysis or debugging.
  • How do I get an API key?

Create a Chroma account and get an API key at Chroma Package Search. You will receive $5 worth of free credits for your queries.

  • What is the benefit of using Chroma Package Search?

It improves the performance of coding agents by providing them with ground truth context about code packages, which helps in reducing errors and hallucinations.

Server Config

{
  "mcpServers": {
    "package-search-mcp": {
      "type": "http",
      "url": "https://mcp.trychroma.com/package-search/v1",
      "headers": {
        "x-chroma-token": "<CHROMA_API_TOKEN>"
      }
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
Chroma
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

2 days ago
Payai X402 Tools

16 hours ago
Payai X402 Tools

16 hours ago
Payai X402 Tools

16 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago