Odel
MCP server: One MCP server.

XKnow Knowledge Base

@techreoneRun by its publisher: served from their own domain, namespace checked by the registry.MCP server · External

Search and explore source-backed SEO, SaaS, and LLM-wiki knowledge from the XKnow knowledge base.

v1.0.2MITTypeScript
Freeno charge per call
How to install

Runs on your machine from its package; the steps are below.

What it does

  1. Reads
  2. Writes
  3. High impact

At most: only reads or looks up information.

What it costs

Free

Odel charges nothing per call. The publisher may charge for its own service.

Runs locally over stdio

This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).

npmxknow-mcpv1.0.2

Run

npx -y xknow-mcp

MCP client config

{
  "mcpServers": {
    "xknow-knowledge-base": {
      "command": "npx",
      "args": [
        "-y",
        "xknow-mcp"
      ]
    }
  }
}
README3 min read

xknow-mcp

npm license MCP

An MCP server for the XKnow Knowledge Base — a curated, cross-linked body of SEO, SaaS, and LLM-wiki knowledge. Give any MCP-capable agent (Claude, Cursor, Cline, opencode, and others) the ability to search and cite it.

  • Local and private. Runs on your machine over stdio. No server, no account, no API key.
  • Static data. The free layer is a snapshot of the public XKnow guides, bundled with the package. Nothing is fetched at query time.
  • Graph-aware. Beyond keyword search, explore_concept walks the cross-links between notes, so an agent can follow a topic instead of getting a flat list.

Quick start

Add it to your MCP client.

Claude Desktop (claude_desktop_config.json), Cursor, Cline, and most clients:

json
{
  "mcpServers": {
    "xknow": {
      "command": "npx",
      "args": ["-y", "xknow-mcp"]
    }
  }
}

Claude Code

bash
claude mcp add xknow -- npx -y xknow-mcp

opencode (opencode.json)

json
{
  "mcp": {
    "xknow": { "type": "local", "command": ["npx", "-y", "xknow-mcp"], "enabled": true }
  }
}

Then ask your agent something like:

"Use the xknow tools to explain keyword difficulty and cite the source." "Search XKnow for SaaS pricing models and summarise the trade-offs."

Tools

ToolWhat it does
search_knowledgeRanked search over the knowledge base. Returns titles, snippets, and URLs.
get_pageFull text of one note by title or slug (preserves [[wikilinks]]).
explore_conceptA note plus its outbound links and backlinks — walks the knowledge graph.
list_topicsLists every note grouped by section (seo, saas, blog).
lint_rulesThe XKnow SEO/SaaS content self-check rubric — each rule with priority (P0–P3), reasoning, fix, and the knowledge-base notes that back it.
citeReturns the canonical citation (title, description, URL) for a note.

Two knowledge layers

LayerContentHow
Free (default)The 57 public XKnow guides and blog postsBundled snapshot — just npx -y xknow-mcp
Full vaultYour purchased XKnow Knowledge Base (500+ linked notes)npx -y xknow-mcp --vault /path/to/SEO-SaaS-Vault

The full-vault mode reads a local folder of Markdown notes, so your purchased copy never leaves your machine. Set it once with the XKNOW_VAULT environment variable if you prefer:

bash
export XKNOW_VAULT="/path/to/SEO-SaaS-Vault"
npx -y xknow-mcp

How it works

xknow-mcp is a Node.js stdio server. The free layer is a static JSON snapshot generated from the public site and bundled in the package (data/knowledge.json); search is a small, dependency-free ranking pass over the bundled notes. Vault mode parses Markdown notes from a local folder on the fly. No network calls, no vector database, no telemetry.

Development

bash
npm install
npm run build:data   # refresh data/knowledge.json from https://xknow.org/mcp/knowledge.json
npm run build        # tsc
npm run smoke        # exercise every tool over a real stdio connection

# also test against a local vault
SMOKE_VAULT=/path/to/SEO-SaaS-Vault npm run smoke

Links

License

MIT — see LICENSE.