We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

Claude Context

MCP server by Zilliz

Index a whole codebase into a vector database and search it semantically from your coding assistant.

Runs locally (Runs on your machine: its page has the install command)Runs with npxNeeds an API key

Install Claude Context

Runs on your machine. Your client starts it with this command:

npx -y @zilliz/claude-context-mcp@latest

Needs Node.js on your computer. The setup steps below show where the command goes in each client.

  • OPENAI_API_KEY secret OpenAI key for embeddings (default provider; EMBEDDING_PROVIDER selects another).
  • MILVUS_TOKEN secret Zilliz Cloud API key or Milvus token.
  • MILVUS_ADDRESS optional Milvus / Zilliz Cloud endpoint (optional for Zilliz Cloud).

Share this server

Opens this page, with the install command and setup steps.

mcp.tc/i/claude-context

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 you 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

Tools

Claude Context lists its tools only to clients with a key, so we can’t show them here.

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.

Set up

Every client starts Claude Context on your machine with the same command. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio claude-context --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --env "MILVUS_TOKEN=<YOUR_MILVUS_TOKEN>" -- npx -y @zilliz/claude-context-mcp@latest
  1. 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
{
  "mcpServers": {
    "claude-context": {
      "command": "npx",
      "args": [
        "-y",
        "@zilliz/claude-context-mcp@latest"
      ],
      "env": {
        "OPENAI_API_KEY": "<YOUR_OPENAI_API_KEY>",
        "MILVUS_TOKEN": "<YOUR_MILVUS_TOKEN>"
      }
    }
  }
}
  1. 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

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "claude-context": {
      "command": "npx",
      "args": [
        "-y",
        "@zilliz/claude-context-mcp@latest"
      ],
      "env": {
        "OPENAI_API_KEY": "<YOUR_OPENAI_API_KEY>",
        "MILVUS_TOKEN": "<YOUR_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
{
  "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
{
  "mcpServers": {
    "claude-context": {
      "command": "npx",
      "args": [
        "-y",
        "@zilliz/claude-context-mcp@latest"
      ],
      "env": {
        "OPENAI_API_KEY": "<YOUR_OPENAI_API_KEY>",
        "MILVUS_TOKEN": "<YOUR_MILVUS_TOKEN>"
      }
    }
  }
}
  1. Refresh the MCP server list in Cascade. Replace the placeholders with your own values.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add claude-context --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --env "MILVUS_TOKEN=<YOUR_MILVUS_TOKEN>" -- npx -y @zilliz/claude-context-mcp@latest

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.claude-context]
command = "npx"
args = ["-y", "@zilliz/claude-context-mcp@latest"]
env = { OPENAI_API_KEY = "<YOUR_OPENAI_API_KEY>", MILVUS_TOKEN = "<YOUR_MILVUS_TOKEN>" }

Needs Node.js on your computer. Replace the placeholders with your own values.

Gemini CLI

gemini mcp add -e "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" -e "MILVUS_TOKEN=<YOUR_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:

{
  "mcpServers": {
    "claude-context": {
      "command": "npx",
      "args": [
        "-y",
        "@zilliz/claude-context-mcp@latest"
      ],
      "env": {
        "OPENAI_API_KEY": "<YOUR_OPENAI_API_KEY>",
        "MILVUS_TOKEN": "<YOUR_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.

Embed

Show Claude Context in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![Claude Context on mcp.tc](https://mcp.tc/i/claude-context/badge.svg)](https://mcp.tc/i/claude-context)
HTML
<a href="https://mcp.tc/i/claude-context"><img src="https://mcp.tc/i/claude-context/badge.svg" alt="Claude Context on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/claude-context.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/claude-context" title="Claude Context on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/claude-context.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Claude Context card to your site.

Markdown
Add the mcp.tc card for Claude Context, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/claude-context.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="claude-context"><a href="https://mcp.tc/i/claude-context">Claude Context on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![Claude Context on mcp.tc](https://mcp.tc/i/claude-context/badge.svg)](https://mcp.tc/i/claude-context)
```

Reference: https://mcp.tc/embed

Change history

This server runs on your computer, so we follow its npm package: each new version shows up here, with edits by its owner.

Follow Claude Context and we’ll email you when something changes.

  1. , Automatic check

    New version 0.1.16 (was 0.1.15). Read from npm.

  2. , Automatic check

    Tracking started: version 0.1.15.

FAQ

Can I paste mcp.tc/i/claude-context into my MCP client?

No. Claude Context runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y @zilliz/claude-context-mcp@latest.

Does Claude Context need an API key?

Yes. It reads OPENAI_API_KEY and MILVUS_TOKEN from its environment, and OPENAI_API_KEY and MILVUS_TOKEN are secrets. Put the values in your client’s config on your own machine, never in a shared file.

Is Claude Context a remote or a local server?

Local. Your client starts it as a process on your computer with npx -y @zilliz/claude-context-mcp@latest, which needs Node.js.

What can Claude Context do?

You can index a codebase into Milvus or Zilliz Cloud, search code with natural language queries and choose OpenAI, VoyageAI, Gemini or Ollama embeddings.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Does mcp.tc track changes to Claude Context?

Partly. It runs on your computer, so we follow its npm package: its History tab shows each new version and edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read Claude Context’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with Zilliz. This page was built from Claude Context’s public metadata, last checked on 3 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.