npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

wiki-nexus

v0.1.1

Published

Zero-server knowledge graph engine for markdown wikis — CLI + MCP tools

Readme

wiki-nexus

Zero-server knowledge graph engine for markdown wikis. Indexes pages, wikilinks, tags, topic clusters, and knowledge flows into SQLite, then exposes them through MCP tools and a REST API.

The core principle: precomputed relational intelligence. All clustering, relationship mapping, staleness detection, and impact analysis is computed at index time — not at query time via expensive LLM multi-hop. Even smaller models get complete structural context in a single tool call.

Install

npm install -g wiki-nexus

Or use without installing:

npx wiki-nexus analyze

Quick start

# Index your wiki
cd ~/my-knowledge-base
wiki-nexus analyze

# See what was built
wiki-nexus status
# → 52 pages, 187 edges, 6 clusters, 0 broken links

# Search
wiki-nexus query "compression methods"

# Hook up to Claude Code
wiki-nexus setup

# Start HTTP API
wiki-nexus serve

CLI commands

| Command | Description | |---------|-------------| | wiki-nexus analyze [path] | Index a wiki directory | | wiki-nexus status | Show index status | | wiki-nexus query <query> | Search the wiki | | wiki-nexus list | List all indexed wikis | | wiki-nexus clean | Delete index | | wiki-nexus mcp | Start MCP server (stdio) | | wiki-nexus serve | Start HTTP API server | | wiki-nexus setup | Configure MCP for your editor |

Flags

wiki-nexus analyze --force             # Full re-index
wiki-nexus analyze --embeddings        # Enable semantic search
wiki-nexus analyze --index-dir ./data  # Custom index location
wiki-nexus serve --port 8080           # Custom port
wiki-nexus query "topic" --limit 5     # Limit results
wiki-nexus clean --all --force         # Delete all indexes

MCP tools

Once indexed, the MCP server exposes 8 tools for AI agents:

| Tool | What it returns | |------|----------------| | wiki_query | Hybrid search results (BM25 + semantic + RRF fusion) | | wiki_context | 360-degree page view — all relationships, clusters, flows, staleness | | wiki_impact | Blast radius — what pages are affected if this page changes | | wiki_clusters | Topic clusters with members and cohesion scores | | wiki_lint | Health check — broken links, orphans, stale pages | | wiki_flows | Knowledge flow tracing from sources through derived pages | | wiki_stats | Wiki-level statistics | | list_wikis | All indexed wikis |

Editor setup

wiki-nexus setup  # Auto-detects Claude Code, Cursor, Codex, Claw Code

Or manually:

Claude Code:

claude mcp add wiki-nexus -- npx wiki-nexus mcp

Cursor (~/.cursor/mcp.json):

{
  "mcpServers": {
    "wiki-nexus": {
      "command": "npx",
      "args": ["wiki-nexus", "mcp"]
    }
  }
}

HTTP API

wiki-nexus serve

| Endpoint | Maps to | |----------|---------| | GET /api/wikis | list_wikis | | GET /api/wikis/:name/stats | wiki_stats | | GET /api/wikis/:name/query?q=... | wiki_query | | GET /api/wikis/:name/pages/:slug/context | wiki_context | | GET /api/wikis/:name/pages/:slug/impact | wiki_impact | | GET /api/wikis/:name/clusters | wiki_clusters | | GET /api/wikis/:name/lint | wiki_lint | | GET /api/wikis/:name/flows | wiki_flows |

Wiki format

WikiNexus works with markdown wikis that use:

  • YAML frontmatter with title, tags, sources, updated
  • [[slug]] wikilinks where slug = filename without .md
  • Flat structure in wiki/pages/
  • SCHEMA.md at wiki root (optional, helps detection)

How it works

  1. Parse — extracts frontmatter, wikilinks, headings from every .md file
  2. Build graph — pages become nodes, wikilinks become edges, stored in SQLite
  3. Cluster — Louvain community detection groups pages into topic clusters
  4. Trace flows — follows how knowledge flows from source documents through derived pages
  5. Analyze — detects broken links, orphan pages, stale content, missing backlinks
  6. Search — BM25 keyword search + optional semantic embeddings with RRF fusion

All computed at index time. MCP tools just read precomputed results.

Packages

| Package | Purpose | |---------|---------| | wiki-nexus | CLI binary + HTTP API | | @wiki-nexus/core | Core indexing engine | | @wiki-nexus/mcp-server | MCP stdio server |

License

MIT