LocalNest MCP

LocalNest MCP is a local-first server unifying semantic code search, a temporal knowledge graph, and persistent AI memory — all powered by SQLite with no cloud dependency. It provides 74 tools across these areas:

Code Intelligence

• Hybrid BM25 + vector semantic search with RRF ranking (search_hybrid)

• Text/regex search across file contents (search_code) and file path search (search_files)

• Symbol definition lookup (get_symbol), call site and import usage finding (find_usages)

• Bounded file reading with line numbers (read_file)

Knowledge Graph & Persistent AI Memory

• Store, recall, update, delete, and list durable memories with tags, scope, confidence, and importance

• Full revision history, semantic deduplication, and agent-scoped isolation

• Capture background events and auto-promote to durable memory (memory_capture_event)

• Link memories with named relations (e.g. "depends_on", "supersedes"), traverse the memory graph, and suggest semantic relations

• Temporal entity-triple store with multi-hop traversal and time-travel queries

Project & Workspace Navigation

• List configured roots and projects, view compact file/directory trees, read file contents

• Generate high-level project summaries (summarize_project)

Indexing & Embeddings

• Build or refresh semantic indexes (index_project), check index and embedding backend status

Agentic Workflows

• Bundle runtime status, memory state, and relevant recall for a task in one call (task_context)

• Capture task outcomes into the memory pipeline, support agent priming and continuous learning

System & Health

• Check server status, run health checks, view usage guidance, check for updates, and self-update

Used for proactive dependency updates as part of the enterprise-grade quality measures, including OpenSSF Scorecard monitoring and Dependabot updates.

Implicitly supported through code intelligence features like symbol finding, AST-aware chunking, and comparison with GitNexus, though not explicitly mentioned as a direct integration target.

Referenced in the README for hosting the project repository, GitHub Actions workflows, and as a comparison point for GitNexus (27k stars), though not as a direct integration target.

Supported data format for ingestion via ingest_markdown tool and as a response format option for many tools, enabling rich text content processing and output.

Referenced as the backend for claude-context (Zilliz), which is a Milvus-backed code intelligence server that LocalNest compares against, noting it lacks knowledge graph and memory features.

Required runtime environment for the MCP server, as indicated by the npm installation method and the note about external dependencies in the feature matrix.

Package distribution platform for the MCP server, with installation via npm install and update functionality through npm, including OIDC Trusted Publishing for verifiable provenance.

Mentioned as a comparison point for memory-only servers, with Basic Memory integrating with Obsidian but lacking code intelligence features that LocalNest provides.

Primary storage backend described as 'Pure SQLite' for the local-first architecture, providing persistent storage for code indexes, knowledge graphs, and memory without cloud dependencies.

1. Click on "Install Server".

2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.

3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@LocalNest MCP find where the user authentication logic is implemented"

That's it! The server will respond to your query, and you can continue using it as needed.

Here is a step-by-step guide with screenshots.