Unified code-context MCP server: structural, lexical and semantic retrieval
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"contextweave-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# ContextWeave Code-context MCP server for coding agents. It gives an agent structural, lexical and semantic retrieval over a repository, so it can pull the definition it needs instead of reading whole files. - **Structural**: tree-sitter symbols, key paths and headings for 27 languages and data/doc formats (`cw languages`). - **Lexical + semantic**: a SQLite index with full-text search and [sqlite-vec](https://github.com/asg017/sqlite-vec) embeddings, fused and packed into a token budget. - **Graph**: callers, callees, imports, inheritance, tests and config edges. Published on PyPI as **`contextweave-mcp`**. The import package is `contextweave` and the commands are `cw` and `contextweave`. ## Install Requires Python 3.14+. ```sh uv tool install contextweave-mcp cw --version ``` ## Quickstart From the root of a project: ```sh cw init # index + wire up Claude Code (default agent) cw status # counts, freshness, daemon and model health cw search "where are retries handled" ``` `cw init` indexes the project and installs the agent integration: MCP server registration, hooks, and a routing block that tells the agent when to use which tool. Remove it again with `cw uninstall` (the index is kept; `cw forget` drops it). | `--agent` | Integration | | ------------- | -------------------------------------------- | | `claude_code` | `.mcp.json`, `.claude/settings.json` hooks and a `CLAUDE.md` block (default) | | `codex` | One global entry in Codex's `config.toml` and an `AGENTS.md` block | | `agents_md` | `.mcp.json` and an `AGENTS.md` block, no hooks | | `none` | Index only | `cw init --plugin` writes a Claude Code plugin directory instead of editing project files. `--dry-run` shows what would change. To run the server by hand for any MCP client: ```sh cw serve # MCP over stdio ``` ## MCP tools | Tool | Use it to …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.