memtrace-index

## Overview Index a local codebase into the persistent code knowledge graph. This is always the first step — it parses every source file, resolves cross-file relationships, detects API endpoints/calls, runs community detection and process tracing, and embeds all symbols for semantic search. ## Quick Reference | Parameter | Purpose | |-----------|---------| | `path` | Absolute path to the directory to index | | `incremental` | Only re-parse changed files (use for subsequent runs) | | `clear_existing` | Wipe and rebuild from scratch | > **Parameter types:** MCP parameters are strictly typed. Numbers (`limit`, `depth`, `min_size`, `last_n`, etc.) must be JSON numbers — not strings. Use `limit: 20`, never `limit: "20"`. Passing a string yields `MCP error -32602: invalid type: string, expected usize`. Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bundled at the memtrace-skills plugin root). ## Steps ### 1. Check if already indexed Use the `list_indexed_repositories` MCP tool first. If the repo is already indexed and recent, skip to step 4. **Success criteria:** You have a list of repo_ids and their last-indexed timestamps. If a repo is present but searches miss a source subdirectory under that repo root (for example `ui/`, `memtrace-ui/`, `web/`, `frontend/`, or `src/`), treat that as a stale/partial index. Do not use grep as a workaround. Run incremental indexing on the repo root, then retry the Memtrace query. ### 2. Index the directory...