Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

NervaPack

by ramdhavepreetamversion 0.5.8i★ –iRuns on your computer
Registry nameio.github.ramdhavepreetam/nervapack

Install

Overview

Description from the maker (original English)

Offline codebase knowledge graph: 91% token reduction vs naive RAG, plus cross-session agent memory.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "nervapack": {
      "command": "uvx",
      "args": [
        "nervapack"
      ]
    }
  }
}

Run this in your terminal

claude mcp add nervapack -- uvx nervapack

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "nervapack": {
      "command": "uvx",
      "args": [
        "nervapack"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "nervapack": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "nervapack"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account ramdhavepreetam, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

  • More stars than 0% of the other 5668 servers in this category
  • Published to the registry more recently than 21% of the other 5668 servers in this category
  • Basic checks equal to or better than 100% of the other 5668 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is NervaPack safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.5.8) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday
Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago
Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 2 months ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

NervaPack

NervaPack is a privacy-first, offline knowledge graph for your codebase. It solves two fundamental problems with standard Vector RAG:

  • Token waste — chunk-based RAG retrieves blobs of text that may only tangentially relate to your query, bloating your context window.
  • Privacy risk — sending code to cloud embedding APIs leaks your proprietary logic.

NervaPack runs 100% on your machine. It uses tree-sitter to parse your codebase into a deterministic Abstract Syntax Tree graph, then uses a local Ollama model to draw hard semantic edges between your documentation and your code. Queries traverse this graph with a K-Hop BFS, returning a hyper-targeted, token-efficient context window — no cloud required.


Verified Performance

91.2% Average Token Reduction — independently verified on real-world codebases.

Test TypeTokens (Naive)Tokens (NervaPack)Reduction
Simple Query10,92610199.1%
Medium Query13,09216498.7%
Complex Query3,2901,10266.5%
Average52,0372,45991.2%

Cost Savings: $181–$724 per developer per year (GPT-4o to Claude Sonnet)

📊 [View Full Benchmarks](docs/BENCHMARKS.md) · 🧪 [Messy Code Performance](docs/MESSY_CODE_PERFORMANCE.md)

Code quality impact: 90–99% reduction on clean code, 50–75% on legacy/messy code. Even poorly structured codebases benefit significantly.


Why NervaPack vs. standard Vector RAG

Standard Vector RAGNervaPack
ParsingArbitrary text chunksDeterministic AST nodes (class, function, import)
RetrievalNearest-neighbour blobK-Hop BFS on a structural graph
Doc ↔ Code linksNoneHard EXPLAINS edges drawn by local LLM
PrivacyCloud embeddings100% local (ChromaDB + ONNX + optional Ollama)
Incremental syncRe-index everythingSurgical per-file update via GitPython diff
Token savingsNo measurementBuilt-in dashboard shows exact reduction per query
Graph visibilityBlack boxInteractive HTML visualization of every node and edge
Duplicate-safeRepeated ingest = duplicate dataupsert — re-ingest is idempotent
Agent memoryNone17-tool MCP server for cross-session memory

Prerequisites

  • Python 3.10+
  • Git — your project must be a git repository (git init if not)

*(Optional for semantic code-doc binding)* — an LLM provider. Structural graph indexing and basic queries work out-of-the-box with zero configuration and no cloud connection.

ProviderSetupCostPrivacy
Ollama (default)brew install ollama && ollama pull llama3Free100% local
Claude APIpip install "nervapack[claude]" + ANTHROPIC_API_KEY~$0.25/1k callsCloud
OpenAI APIpip install "nervapack[openai]" + OPENAI_API_KEY~$0.15/1k callsCloud
MCP (Claude Code)Zero configIncluded in subscriptionCloud

Installation

# Recommended

pip install nervapack

With optional features

pip install "nervapack[mcp]" # MCP server for Claude Code / Cursor pip install "nervapack[memory]" # agent memory MCP server pip install "nervapack[metrics]" # exact token counts (tiktoken) pip install "nervapack[dashboard]" # web dashboard (streamlit + plotly) pip install "nervapack[claude]" # Claude API support pip install "nervapack[openai]" # OpenAI API support pip install "nervapack[all]" # everything

On first run, ChromaDB downloads an ONNX embedding model (~30 MB) to ~/.cache/chroma/. This is a one-time download.


Quick Start

cd your-project/

1. Build the knowledge graph (runs locally, no LLM required for basic use)

nervapack ingest .

2. Query for context — get focused results + token savings dashboard

nervapack query "How does authentication work?"

3. Add semantic doc-to-code edges (requires an LLM)

nervapack enrich .

4. Visualize the full graph

nervapack visualize --enhanced --communities

5. After changing files, sync incrementally (fast — only changed files)

nervapack sync .

6. If you ingested wrong data or need a fresh start

nervapack clean --all nervapack ingest .

7. Check system health

nervapack doctor


Command Reference

nervapack ingest [PATH] — Build the graph

Scans PATH (default: .) and builds the full knowledge graph.

What happens:

  1. Walks the directory tree with tree-sitter, skipping dist/, build/, node_modules/, venv/, site/, .tox/, and dozens of other build directories automatically.
  2. Parses source files into exact AST nodes: classes, functions, imports.
  3. Chunks all .md files by header hierarchy.
  4. Embeds every entity into a local ChromaDB vector store (ONNX by default, Ollama optional).
  5. Optionally binds doc chunks to code nodes via an LLM, adding EXPLAINS edges.
  6. Saves the graph once to .nervapack/graph.graphml.

Re-ingesting is safe — upsert is used throughout, so running ingest twice does not duplicate data.

nervapack ingest .                           # auto-detect LLM

nervapack ingest . --llm ollama # force Ollama nervapack ingest . --llm claude # use Claude API nervapack ingest . --llm openai --model gpt-4o-mini nervapack ingest . --embeddings ollama # use Ollama for embeddings too

Supported languages (bundled): Python, JavaScript, JSX, TypeScript, TSX

Additional languages:

pip install "nervapack[go]"            # Go

pip install "nervapack[rust]" # Rust pip install "nervapack[java]" # Java pip install "nervapack[c]" # C / C headers pip install "nervapack[cpp]" # C++ pip install "nervapack[ruby]" # Ruby pip install "nervapack[csharp]" # C# pip install "nervapack[all-languages]" # all of the above

Exclude directories — create .nervapackignore in your project root (gitignore syntax):

dist/

build/ site/ generated/ *.egg-info/


nervapack query PROMPT — Query the graph

Retrieves focused context for a natural-language prompt and prints a token savings dashboard.

What happens:

  1. Intent detection — "what breaks if I change X" routes to impact analysis (reverse BFS); exact symbol names bypass vector search.
  2. ChromaDB returns the top-3 most semantically similar nodes.
  3. Those nodes seed a K-Hop BFS through the NetworkX graph (default: 1 hop, both directions).
  4. Adjacent nodes — including any markdown docs via EXPLAINS edges and memory notes via TOUCHES edges — are collected.
  5. A focused Markdown context block is printed, ready to paste into an LLM prompt.
  6. Token efficiency panel shows savings vs. naive "dump the whole file" RAG.
nervapack query "How does authentication work?"

nervapack query "What calls VectorStore?" nervapack query "what breaks if I change GraphBuilder" # impact analysis

Example output:

Query: "How does authentication work?"

Query Router: Intent: semantic, Direction: both Vector Search: Found 3 seed nodes

Retrieved Context: ──────────────────────────────────────────────────────────

NervaPack Context Retrieval

File: src/auth/middleware.py

CLASS: AuthMiddleware (L15-L42)

... ──────────────────────────────────────────────────────────

╭────────────── NervaPack Token Efficiency ──────────────╮ │ Strategy Tokens Reduction │ │ Naive RAG (3 files) 12,840 100% (base) │ │ NervaPack 1,180 9.2% │ │ ─────────────────────────────────────────────────────────│ │ Tokens saved: 11,660 Reduction: 90.8% │ │ Cost saved (GPT-4o $2.50/1M): $0.0292 per query │ ╰───────────────────────────────────────────────────────────╯


nervapack sync [PATH] — Incremental update

Updates only the files that changed since the last ingest. Uses GitPython to diff the working tree.

nervapack sync .

A full ingest on a large project can take minutes. sync turns that into a 2–5 second surgical update per file. Re-parses changed files, batch-upserts new vectors, and saves the graph once at the end.


nervapack clean [OPTIONS] — Remove ingested data

Wipe graph data and start fresh. Use this when you have duplicate vectors, ingested the wrong directory, or need to reduce disk usage.

nervapack clean --vectors          # wipe ChromaDB only (chroma_db/)

nervapack clean --graph # delete graph.graphml only nervapack clean --history # clear query + graph history logs nervapack clean --all # everything above (keeps memory.db) nervapack clean --all --yes # skip confirmation (CI / scripts)

Never deleted by `clean`: memory.db — your agent memory is always safe.

Typical workflow after a bad ingest:

nervapack clean --all

nervapack ingest .


nervapack enrich [PATH] — Add semantic edges

Runs LLM doc-to-code binding on an already-ingested graph. Use this if you:

  • Ran ingest without an LLM and want to add EXPLAINS edges now.
  • Added new documentation and want to bind it without a full re-ingest.
nervapack enrich .                           # auto-detect LLM

nervapack enrich . --llm ollama --model llama3 nervapack enrich . --llm claude # shows cost estimate before proceeding


nervapack status [--detailed] — Graph health
nervapack status            # node/edge counts + unsynced files

nervapack status --detailed # full analytics: health score, language distribution, coverage

Health score (0–100) factors in documentation coverage, node connectivity, graph density, and edge diversity. A structural-only graph typically scores 30–40; after enrich it rises to 70–90.


nervapack visualize [OPTIONS] — Interactive HTML graph
nervapack visualize                           # basic visualization

nervapack visualize --enhanced # + real-time search + path finder nervapack visualize --enhanced --communities # + community detection (Louvain) nervapack visualize --output ~/my-graph.html # custom output path nervapack visualize --no-browser # generate without opening

Produces a standalone HTML file with no external dependencies — drag, zoom, search, find shortest paths between nodes.


nervapack explore TARGET [--hops N] — Focused subgraph

Extract and visualize the N-hop neighbourhood of a specific file, class, or function.

nervapack explore GraphBuilder --hops 2

nervapack explore src/auth/middleware.py --hops 1 nervapack explore "function:parse"


nervapack dependencies [FILE] — Import dependency analysis

Analyze file-level import chains, detect circular dependencies, and visualize the dependency graph.

nervapack dependencies                        # full project analysis

nervapack dependencies src/graph/builder.py # single file nervapack dependencies --no-cycles # skip cycle detection


`nervapack hotspots [

Only the beginning is shown; read the rest in the repo

Ask PopNx