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

@foor.tech/livewiki-mcp

v1.1.1

Published

MCP server that exposes a LiveWiki tenant's search + RAG to any MCP-capable AI client (Claude Code, Codex, Cursor, Zed, Copilot).

Readme

@foor.tech/livewiki-mcp

LiveWiki over MCP — turn your team's knowledge base into a pluggable tool for any MCP-capable AI client (Claude Code, OpenAI Codex, Cursor, Zed, GitHub Copilot, …).

One index, many clients. Your AI tools query the same authoritative wiki your team already edits.

New to LiveWiki? Spin up a workspace at livewiki.foor.tech, drop in a Confluence export, MediaWiki dump, or a folder of docs — then plug this MCP server into your editor and ask questions across everything.


What it gives your AI

Five tools, all scoped to the tenant you configure:

| Tool | Purpose | |---|---| | livewiki_search | Semantic (default) or keyword search across pages. Optional wiki_slugs: string[] to scope to one or several wikis. | | livewiki_ask | RAG Q&A with source citations — ideal when the user has a direct question. Optional wiki_slugs: string[] to scope the retrieval. | | livewiki_list_wikis | Discover the wikis available in the workspace. | | livewiki_list_pages | List pages in a specific wiki. | | livewiki_get_page | Read the full markdown body of a page. |

Scoping to specific wikis

Both livewiki_search and livewiki_ask accept an optional wiki_slugs array. Examples:

// One wiki
{ "query": "refunds on staging", "wiki_slugs": ["runbooks"] }

// Two or three wikis — the model picks a union
{ "question": "how do we onboard a new hire?", "wiki_slugs": ["onboarding", "engineering-handbook"] }

// Omit entirely to search every wiki in the workspace
{ "query": "incident response" }

Call livewiki_list_wikis first if your assistant doesn't already know which slugs exist. The deprecated singular wiki_slug is still accepted as an alias for a one-element array — wiki_slugs takes precedence if both are passed.

Retrieval runs server-side on LiveWiki's backend — HeliosDB (PostgreSQL-compatible own-engine with the native vector storage and managed for HA) stores content + embeddings; Voyage AI (voyage-3.5-lite, 1024-dim) produces the vectors at ingest time. Your AI client pays only for the tokens in its own prompt, not for re-embedding on every query.


Install

Pick whichever style fits your workflow:

Run on demand (recommended for editors) — no install needed; each session fetches the latest:

npx -y @foor.tech/livewiki-mcp

Global install — put livewiki-mcp on your PATH:

npm install -g @foor.tech/livewiki-mcp
livewiki-mcp --base-url=https://livewiki-api.foor.tech --tenant=my-workspace --token=lw_…

Per-project install — pin an exact version:

npm install --save-dev @foor.tech/livewiki-mcp
npx livewiki-mcp

All editor snippets below use the npx -y form — it's stateless and works across machines without pre-installation.


Configure

Three environment variables (or equivalent CLI flags):

| Variable | Flag | Example | |---|---|---| | LIVEWIKI_API_URL | --base-url | https://livewiki-api.foor.tech | | LIVEWIKI_TENANT | --tenant | my-workspace | | LIVEWIKI_API_TOKEN | --token | lw_… (Settings → API tokens) |

Generate a token in your LiveWiki workspace under Settings → API tokens (direct link: livewiki.foor.tech/<your-tenant>/settings). The token is shown once at creation — copy it immediately; only a short prefix is retained afterwards.


Wire it into your editor

Claude Code

~/.claude/settings.json:

{
  "mcpServers": {
    "livewiki": {
      "command": "npx",
      "args": ["-y", "@foor.tech/livewiki-mcp"],
      "env": {
        "LIVEWIKI_API_URL": "https://livewiki-api.foor.tech",
        "LIVEWIKI_TENANT": "my-workspace",
        "LIVEWIKI_API_TOKEN": "lw_…"
      }
    }
  }
}

Restart Claude Code or run /mcp to verify.

OpenAI Codex CLI

~/.codex/config.toml:

[mcp_servers.livewiki]
command = "npx"
args = ["-y", "@foor.tech/livewiki-mcp"]
env = { LIVEWIKI_API_URL = "https://livewiki-api.foor.tech", LIVEWIKI_TENANT = "my-workspace", LIVEWIKI_API_TOKEN = "lw_…" }

Cursor

.cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "livewiki": {
      "command": "npx",
      "args": ["-y", "@foor.tech/livewiki-mcp"],
      "env": {
        "LIVEWIKI_API_URL": "https://livewiki-api.foor.tech",
        "LIVEWIKI_TENANT": "my-workspace",
        "LIVEWIKI_API_TOKEN": "lw_…"
      }
    }
  }
}

Zed

~/.config/zed/settings.json:

{
  "context_servers": {
    "livewiki": {
      "command": {
        "path": "npx",
        "args": ["-y", "@foor.tech/livewiki-mcp"],
        "env": {
          "LIVEWIKI_API_URL": "https://livewiki-api.foor.tech",
          "LIVEWIKI_TENANT": "my-workspace",
          "LIVEWIKI_API_TOKEN": "lw_…"
        }
      }
    }
  }
}

GitHub Copilot (VS Code 1.95+)

.vscode/mcp.json (project) or user settings:

{
  "servers": {
    "livewiki": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@foor.tech/livewiki-mcp"],
      "env": {
        "LIVEWIKI_API_URL": "https://livewiki-api.foor.tech",
        "LIVEWIKI_TENANT": "my-workspace",
        "LIVEWIKI_API_TOKEN": "lw_…"
      }
    }
  }
}

Scope guidance for your model

Include a short prompt hint in your CLAUDE.md / .cursorrules / etc. so the model reaches for LiveWiki in the right situations:

You have access to a LiveWiki workspace via livewiki_* tools. When the user asks a "how do we…", "where is the doc for…", "what did we decide about…" style question that may be answered by team docs, call livewiki_ask first. If that returns low-relevance sources, fall back to livewiki_search with mode: "semantic".


What LiveWiki is

LiveWiki is an AI-powered wiki platform — modern MediaWiki replacement with auto-organize, stale detection, RAG Q&A, cross-links, and migration tools (MediaWiki, Confluence XML/HTML/Cloud, drop-and-organize for arbitrary files). This package is the MCP surface that exposes its retrieval to external AI clients.

Learn more and create a workspace: livewiki.foor.tech


Development

git clone https://github.com/FOOR-tech/livewiki-mcp
cd livewiki-mcp
npm install
npm run build
LIVEWIKI_API_URL=… LIVEWIKI_TENANT=… LIVEWIKI_API_TOKEN=… node dist/cli.js

The server speaks MCP over stdio. For an interactive sanity check, point an MCP inspector at it.


Links

  • LiveWiki: livewiki.foor.tech
  • HeliosDB: heliosdb.com/lite.html
  • Voyage AI: voyageai.com
  • Source: github.com/FOOR-tech/livewiki-mcp
  • npm: npmjs.com/package/@foor.tech/livewiki-mcp
  • MCP spec: modelcontextprotocol.io

License

MIT © foor.tech