Client-neutral semantic code indexing and search MCP: standalone indexes plus read-only Roo Code compatibility.
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":"roo-code-index-bridge-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.
# Roo Code Index Bridge MCP A client-neutral, local-first **semantic code indexing and search MCP**. Version 0.6.0 owns the whole indexing pipeline — file discovery, structural chunking, embeddings, Qdrant storage, incremental sync, and watching — so **Roo Code is not required**. It works from any MCP-compatible client. One-click setup targets: Codex, Claude Code, ZCode, VS Code, VS Code (workspace), and OpenCode. ChatGPT desktop can use the bridge through a local Codex host that shares Codex's MCP configuration — see [docs/installation.md](docs/installation.md#chatgpt-desktop-via-a-local-codex-host). ChatGPT web / remote MCP endpoints are not local-stdio targets and are out of scope. Legacy Roo Code `ws-*` indexes remain searchable **read-only** for backward compatibility. ## Architecture in One Page ``` MCP client (Codex/ZCode/Claude Code/VS Code/...) │ stdio ▼ FastMCP server (server.py — registration only) ▼ IndexBridgeService (service.py — policy + orchestration) │ ├─ FileDiscovery → git ls-files / safe walk, .gitignore + .rooignore, size/binary/symlink guards ├─ Chunker → tree-sitter structural chunks, markdown headings, line fallback ├─ EmbeddingClient→ Ollama /api/embed batches (also OpenAI-compatible, Gemini, Mistral) ├─ QdrantStore → rci-* collections, batched upserts, ownership checks, alias swaps ├─ StateDB → SQLite (platform data dir, see docs/configuration.md) └─ WatchManager → debounced watchfiles → one incremental sync ``` Details: [docs/architecture.md](docs/architecture.md) · Tools: [docs/mcp-tools.md](docs/mcp-tools.md) · Installation & setup: [docs/installation.md](docs/installation.md) · Configuration: [docs/configuration.md](docs/configuration.md) · Problems: [docs/troubleshooting.md](docs/troubleshooting.md) ## Requirements - The launcher installs [uv](https://docs.astral.sh/uv/) and managed Python 3.11+ as needed. - Healthy configured *…
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.