# Claude Context MCP server > Index a whole codebase into a vector database and search it semantically from your coding assistant. - Listing: https://mcp.tc/i/claude-context - Connect: this is a local (stdio) server; install it on your machine (see Install). The listing link is a page, not an MCP endpoint. - Type: local (stdio) - Auth: API key - Category: [Developer Tools](https://mcp.tc/c/developer-tools) - Vendor: Zilliz - Repository: - Package: npm `@zilliz/claude-context-mcp` ## About Claude Context indexes a codebase into a Milvus or Zilliz Cloud vector database and lets an AI coding assistant search it with natural language. Code is split into chunks and embedded, so the assistant can pull relevant code from a large repository into context instead of loading whole directories. It runs locally over stdio with npx. It needs an API key for an embedding provider (OpenAI by default, or VoyageAI, Gemini or Ollama) and a Milvus address and token, for example from Zilliz Cloud. Optional settings cover custom file extensions, ignore patterns, batch size and collection naming. ## What it can do - Index a codebase into Milvus or Zilliz Cloud - Search code with natural language queries - Choose OpenAI, VoyageAI, Gemini or Ollama embeddings - Add custom file extensions and ignore patterns - Keep the index updated with background sync and a trigger file ## Example prompts - "Index this repository so I can search it semantically." - "Find where user authentication is handled in this codebase." - "Search the indexed project for code that retries failed HTTP requests." - "Re-index the project after my latest changes." ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport stdio claude-context --env "OPENAI_API_KEY=" --env "MILVUS_TOKEN=" -- npx -y @zilliz/claude-context-mcp@latest ``` 2. Start Claude Code and type `/mcp`. **claude-context** should show as connected. Add `--scope user` to make it available in every project. Replace the placeholders with your own values. ### Claude Desktop 1. Open **Settings → Developer → Edit Config**. It opens `claude_desktop_config.json`. Add: `claude_desktop_config.json`: ```json { "mcpServers": { "claude-context": { "command": "npx", "args": [ "-y", "@zilliz/claude-context-mcp@latest" ], "env": { "OPENAI_API_KEY": "", "MILVUS_TOKEN": "" } } } } ``` 2. Save the file and restart Claude Desktop. Replace the placeholders with your own values. Needs Node.js on your computer. The file lives in `~/Library/Application Support/Claude/` on macOS and `%APPDATA%\Claude\` on Windows. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "claude-context": { "command": "npx", "args": [ "-y", "@zilliz/claude-context-mcp@latest" ], "env": { "OPENAI_API_KEY": "", "MILVUS_TOKEN": "" } } } } ``` Needs Node.js on your computer. Replace the placeholders with your own values. ### VS Code Add it to `.vscode/mcp.json`. VS Code asks for the secret the first time and stores it securely: `.vscode/mcp.json`: ```json { "servers": { "claude-context": { "type": "stdio", "command": "npx", "args": [ "-y", "@zilliz/claude-context-mcp@latest" ], "env": { "OPENAI_API_KEY": "${input:openai-api-key}", "MILVUS_TOKEN": "${input:milvus-token}" } } }, "inputs": [ { "type": "promptString", "id": "openai-api-key", "description": "OPENAI_API_KEY", "password": true }, { "type": "promptString", "id": "milvus-token", "description": "MILVUS_TOKEN", "password": true } ] } ``` Needs Node.js on your computer. ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "claude-context": { "command": "npx", "args": [ "-y", "@zilliz/claude-context-mcp@latest" ], "env": { "OPENAI_API_KEY": "", "MILVUS_TOKEN": "" } } } } ``` 2. Refresh the MCP server list in Cascade. Replace the placeholders with your own values. Devin Desktop is the new name for Windsurf. ### Codex ```bash codex mcp add claude-context --env "OPENAI_API_KEY=" --env "MILVUS_TOKEN=" -- npx -y @zilliz/claude-context-mcp@latest ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.claude-context] command = "npx" args = ["-y", "@zilliz/claude-context-mcp@latest"] env = { OPENAI_API_KEY = "", MILVUS_TOKEN = "" } ``` Needs Node.js on your computer. Replace the placeholders with your own values. ### Gemini CLI ```bash gemini mcp add -e "OPENAI_API_KEY=" -e "MILVUS_TOKEN=" claude-context npx -- -y @zilliz/claude-context-mcp@latest ``` This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients that start local servers accept this shape: ```json { "mcpServers": { "claude-context": { "command": "npx", "args": [ "-y", "@zilliz/claude-context-mcp@latest" ], "env": { "OPENAI_API_KEY": "", "MILVUS_TOKEN": "" } } } } ``` Zed puts servers under `context_servers` in its settings, with the same `command`, `args` and `env` fields. Needs Node.js on your computer. Replace the placeholders with your own values. ## Details - Server version: 0.1.15 - Last checked: 2026-10-03 - Listed: 2026-10-03 - Updated: 2026-10-03 --- Source: https://mcp.tc/i/claude-context (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report