astroid-mcp

# Astroid (astroid-mcp) High-performance, local FastEmbed ONNX vector + SQLite FTS5 Model Context Protocol (MCP) server for Astro documentation. - **Hybrid search**: 384-dim BAAI/bge-small-en-v1.5 embeddings + SQLite FTS5 BM25, fixed candidate pools, deterministic rankings. - **Clean chunks**: heading-aware splitting, tiny-section merging, cross-doc dedupe; every chunk fully inside the model's 512-token window (zero silent truncation). - **Native stdio**: local execution, zero network ports. - **Additive-only installer**: never rewrites your existing MCPs or settings. ## Install (Windows and WSL — same package, simultaneously) One wheel (`py3-none-any`) serves both OSes. Install it as an *application* so the `astroid` command lands on PATH: `pipx install` or `uv tool install`. Plain `pip install` / `uv pip install` only drops the library into a Python environment (no command on PATH) — if you went that way by habit and get `astroid: command not found`, reinstall with one of the two below. What `astroid install` does — all three, every time: 1. Registers the server in the global OpenCode config (one additive entry; sibling MCPs, comments, and formatting are preserved). 2. Copies the prebuilt docs database into the per-OS user path (see table below). An existing database is left byte-identical. 3. Downloads the embedding model (~70 MB, once per OS — shared with other MCPs using the same model) into the per-OS model cache (see table below). Offline? The config entry still applies; the data steps print a skip line and happen on the first search instead — so the first answer is the slow one, never the install. Windows (PowerShell): ```powershell pipx install astroid-mcp # or: uv tool install astroid-mcp astroid install astroid search "routing" --limit 1 # verify: expect routing docs back ``` WSL / Linux (bash). The `export` line is one-time setup — persist it so every new shell finds the command: ```bash uv tool install astroid-mcp # or: pipx…