my_wiki/raw/llm_wiki/mcp-server/README.md

LLM Wiki MCP Server

This package exposes the running LLM Wiki desktop app as a Model Context Protocol server.

It does not scan project folders directly and does not copy the app's search or graph logic. Every tool calls the local desktop API at http://127.0.0.1:19828/api/v1, so MCP clients use the same project registry, file permissions, search backend, graph backend, and Source Watch rules as the app.

Requirements

• Node.js 20+
• LLM Wiki desktop app running
• Settings → API + MCP → "Enable local HTTP API"
• Settings → API + MCP → "Enable MCP access"
• Either:
  • Settings → API + MCP → "Allow access without a token", or
  • LLM_WIKI_API_TOKEN set to the configured API token

Optional:

• LLM_WIKI_API_BASE_URL to override the default API base URL.

Build

cd mcp-server
npm install
npm run build

Run

LLM_WIKI_API_TOKEN=your-token node dist/src/index.js

Example MCP client config:

{
  "mcpServers": {
    "llm-wiki": {
      "command": "node",
      "args": ["/absolute/path/to/llm_wiki/mcp-server/dist/src/index.js"],
      "env": {
        "LLM_WIKI_API_TOKEN": "your-token"
      }
    }
  }
}

When API unauthenticated mode is enabled, omit LLM_WIKI_API_TOKEN. If MCP access is disabled in Settings, llm_wiki_status still works for diagnosis but other tools return an explicit disabled error.

Tools

• llm_wiki_status: health and current project summary.
• llm_wiki_projects: known projects and active project.
• llm_wiki_set_project: pin the MCP process session to a project. Once pinned, other project tools reject attempts to access a different project.
• llm_wiki_files: list project files. project_id can be a project UUID, a project filesystem path, or current.
• llm_wiki_read_file: read an allowed text file such as wiki/index.md.
• llm_wiki_reviews: list Review tab items. Defaults to unresolved items and supports status, type, and limit filters.
• llm_wiki_search: search with the app's shared keyword/vector backend.
• llm_wiki_chat: ask the backend Agent chat endpoint and receive answer text, references, usage, and tool events. mode: deep broadens backend evidence collection; full Deep Research workflows still live in the desktop app.
• llm_wiki_graph: query the app's knowledge graph endpoint.
• llm_wiki_rescan_sources: trigger a Source Watch rescan using the user's configured rules.

Security model

The MCP server inherits the desktop API's security model:

• It only talks to 127.0.0.1 by default.
• It uses the same API token or unauthenticated setting as Settings → API + MCP.
• File reads go through the API path allow-list. Internal app state files are not exposed.
• Review data is exposed only through the dedicated Review endpoint/tool, which defaults to unresolved items rather than opening internal state files directly.
• Search and graph tools operate on projects known to the app; use project_id: "current" for the active project.
• For multi-project use, call llm_wiki_set_project once. The resolved project ID remains fixed for the lifetime of the MCP subprocess even if the desktop UI switches projects, and every project-tool response includes an activeProject marker.

Do not pass API tokens via command-line arguments. Prefer environment variables so they do not appear in shell history.