local-rag-mcplisted

# Local RAG MCP ## When to use Use when the task requires semantic search over a local document corpus and an appropriate local RAG MCP server is available. Prefer standard grep/glob for simple pattern matching — RAG adds value for conceptual queries and cross-document synthesis. ## Requirements / Checks - Verify a local RAG MCP server is configured (`apx mcp list` or check MCP settings). - Do NOT attempt to install or spin up Docker containers for vector databases without explicit user permission. - Confirm whether the embedding provider is local or remote — if remote (e.g., OpenAI), warn the user before ingesting sensitive content. ## Workflow 1. **Identify need** — determine whether the query requires semantic retrieval (conceptual, cross-document) vs. standard grep/glob (exact pattern, single file). 2. **Check configuration** — verify the connection to the local RAG MCP server. If it fails, surface the error rather than falling back silently. 3. **Inventory corpus** — use status or list tools to see what's already indexed before ingesting anything. 4. **Ingest (only if necessary)** — ingest only files explicitly approved for this corpus. Include clear source metadata (file path, ingest timestamp). Exclude: `.env` files, credential files, SSH keys, and files outside the workspace. 5. **Query strategy**: - Start with the user's exact terms; do not paraphrase into broader concepts. - Add one specific disambiguating detail if initial results are too broad. -