Claude Context (Zilliz)
Semantic code search over your whole codebase for Claude Code and other coding agents.
Sources and review
Checked against public documentation on . Suitability guidance is our editorial judgment; this is not a performance benchmark or an endorsement.
Very large codebases where grep-and-read exploration burns too much context.
You can't use an embedding API and a Milvus or Zilliz Cloud instance; both are required.
About Claude Context (Zilliz)
Claude Context, from Zilliz, adds semantic code search to Claude Code and other AI coding agents. It indexes a codebase into a vector database and brings only the relevant code into context, which the authors present as cheaper than loading whole directories for large codebases. It needs an embedding provider, OpenAI by default with alternatives supported, and a Milvus or Zilliz Cloud vector database.
Claude Context (Zilliz) is listed in this index written primarily in TypeScript, with 13k stars on GitHub. Its latest recorded repository push was in July 2026; that is not an ASE editorial review date.
Before connecting: access and data
This record's specific permissions have not been reviewed by ASE. Read the publisher's documentation before copying setup or connecting.
- List the accounts, files and services the enabled tools can read, change or execute. Check your actual credentials and discovered tools.
- Use narrowly scoped credentials and read-only mode where supported. Review proposed writes before approving them; a generated configuration does not apply these limits for you.
- Local launch is not local-only data processing. External services receive requests, and your client may pass tool results to its model provider. Check both destinations before sharing private data.
- Keep keys and browser session files out of shared config, repositories and screenshots. Know how to disconnect the server and separately revoke its credentials or account sessions.
Add Claude Context (Zilliz) to your MCP client
Generated from the launch command in the project's README. Your client starts the server on demand. Replace <your-key>, <your-endpoint> and <your-token> with your own values first.
Claude Code
claude mcp add claude-context -e 'OPENAI_API_KEY=<your-key>' -e 'MILVUS_ADDRESS=<your-endpoint>' -e 'MILVUS_TOKEN=<your-token>' -- npx @zilliz/claude-context-mcp@latestCursor
{
"mcpServers": {
"claude-context": {
"command": "npx",
"args": ["@zilliz/claude-context-mcp@latest"],
"env": {
"OPENAI_API_KEY": "<your-key>",
"MILVUS_ADDRESS": "<your-endpoint>",
"MILVUS_TOKEN": "<your-token>"
}
}
}
}VS Code
{
"servers": {
"claude-context": {
"type": "stdio",
"command": "npx",
"args": ["@zilliz/claude-context-mcp@latest"],
"env": {
"OPENAI_API_KEY": "<your-key>",
"MILVUS_ADDRESS": "<your-endpoint>",
"MILVUS_TOKEN": "<your-token>"
}
}
}
}Claude Desktop
{
"mcpServers": {
"claude-context": {
"command": "npx",
"args": ["@zilliz/claude-context-mcp@latest"],
"env": {
"OPENAI_API_KEY": "<your-key>",
"MILVUS_ADDRESS": "<your-endpoint>",
"MILVUS_TOKEN": "<your-token>"
}
}
}
}Codex
[mcp_servers.claude-context]
command = "npx"
args = ["@zilliz/claude-context-mcp@latest"]
env = { OPENAI_API_KEY = "<your-key>", MILVUS_ADDRESS = "<your-endpoint>", MILVUS_TOKEN = "<your-token>" }