Wikijs MCP Server

wikijs-mcp

A Model Context Protocol (MCP) server for Wiki.js, the self-hosted wiki that keeps its pages as markdown and exposes everything through one GraphQL endpoint.

Lets MCP clients like Claude Code, Claude Desktop or Codex search, read and edit wiki pages — and, if you let them, manage its assets, comments, users, groups and maintenance jobs.

Sixty-two tools is the ceiling, not the floor: WIKIJS_ALLOW_TOOLS=essential registers a curated seven instead, and a model picks the right tool far more reliably from seven than from sixty-two — see choosing which tools load.

Requirements

• Node.js ≥ 22
• A running Wiki.js instance and an API token

Configuration

The locale is part of a page's identity, not a display preference: the same path under en and de is two different pages. On a wiki set up in another language, set WIKIJS_LOCALE or every lookup by path answers "not found". list_locales reports what is installed.

API keys are administrative. Wiki.js offers "full access" or a group, and a full-access key can rewrite every page and every account. WIKIJS_READ_ONLY, WIKIJS_ALLOWED_PATHS and the key's own group permissions are three independent ways to narrow that — see SECURITY.md.

Use https://. Over plain http the token travels unencrypted; the server prints a warning unless the host is local. For self-signed certificates prefer a proper internal CA over WIKIJS_INSECURE_TLS.

Without credentials the server still starts and lists its tools (so registries and inspectors can introspect it), but every call fails with setup instructions instead of reaching the API.

Choosing which tools load

WIKIJS_ALLOW_TOOLS and WIKIJS_DENY_TOOLS take comma-separated tool names; a trailing * matches a whole family. essential is a curated preset — search_pages, grep_pages, get_page, list_pages, get_page_tree, create_page and update_page, which is what it takes to find, read and write a wiki page end to end — marked as such in the tool reference.

WIKIJS_ALLOW_TOOLS=essential
WIKIJS_ALLOW_TOOLS=get_page,search_pages,list_*
WIKIJS_DENY_TOOLS=delete_*,purge_page_history,set_api_state

An entry that matches no tool aborts startup and names it, so a typo cannot silently hide a tool — an absent tool is not something anyone traces back to an environment variable. A filtered tool is never registered, so it is absent from tools/list and unknown to tools/call alike, exactly like a write tool under WIKIJS_READ_ONLY.

If you run several of these servers at once, mcp-hub is the other answer — its /hub endpoint replaces every server's tools with six meta-tools.

Confining writes to part of the wiki

WIKIJS_ALLOWED_PATHS limits the writing page and asset tools to a set of path prefixes. Reads stay unrestricted, deliberately: a scope on reads turns a wiki into a confusing half-wiki, and the API key's own page rules are the right place to hide pages outright — they hide them from the web UI too.

WIKIJS_ALLOWED_PATHS=docs,team/notes

Matching is by path segment, so docs covers docs/setup and not docs-archive/old. move_page checks both ends, so a page cannot be moved out of the allowed area or into a protected one.

Asset writes are checked against the asset folder tree, which is a separate namespace. The operations that cannot be confined to a prefix at all — the instance-wide maintenance tools, the tag tools, and comment edits, because Wiki.js does not say which page a comment is on — refuse while the variable is set rather than making a silent exception.

Installation

Claude Code

claude mcp add wikijs-mcp -- npx -y @ni-c/wikijs-mcp

Claude Desktop

{
  "mcpServers": {
    "wikijs-mcp": {
      "command": "npx",
      "args": ["-y", "@ni-c/wikijs-mcp"],
      "env": {
        "WIKIJS_URL": "https://wiki.example.com",
        "WIKIJS_TOKEN": "…"
      }
    }
  }
}

Codex

[mcp_servers.wikijs-mcp]
command = "npx"
args = ["-y", "@ni-c/wikijs-mcp"]
env = { WIKIJS_URL = "https://wiki.example.com", WIKIJS_TOKEN = "…" }

Docker

docker run --rm -i \
  -e WIKIJS_URL=https://wiki.example.com \
  -e WIKIJS_TOKEN=… \
  ghcr.io/ni-c/wikijs-mcp

Tools

62 tools. ★ marks the essential preset; ⚠ marks a tool that needs a confirmation token.

The full reference, with every parameter, is at wikijs-mcp.ni-c.de/reference/tools.

Two things worth knowing before you use search_pages

Wiki.js' default search engine does not index page content. "Database - Basic" matches titles and descriptions only, so searching for a phrase written inside a page returns nothing at all. search_pages reports which engine is active and says so; grep_pages fetches pages and matches their text locally, which is slower and actually finds things. Switching the wiki to the PostgreSQL or Elasticsearch engine and running rebuild_search_index fixes it properly.

update_page refuses to overwrite somebody else's edit. It compares the page against the moment you read it, not against its own read a millisecond earlier, so an edit saved from the web UI while the model was thinking is caught rather than silently discarded. get_page_conflict shows the newer version; force: true overwrites on purpose.

Safety

• Destructive and administrative tools are two-step. The first call returns a short-lived confirmation token bound to the exact target; only a second call carrying that token performs the operation. A model cannot satisfy this gate on its own. The binding includes everything that decides what is touched — a token for migrate_pages_locale from de to en will not run en to de.
• Confirmation prompts never quote content from Wiki.js. Page titles and descriptions are written by anyone with edit rights, and that text is read by a model. Only ids, paths and server-side values appear, and a path is checked to be an identifier before it is interpolated.
• Returned page content is marked as untrusted data, because a wiki is exactly a place where text is stored to be read later.
• There is no tool that creates an API key, although the Wiki.js API offers one: a model able to mint a full-access key could grant itself administrative access that outlives this session. list_api_keys and revoke_api_key are here so keys can be audited and taken away.
• Credentials are deleted from the environment after startup, secrets in API responses are redacted, error bodies are truncated and HTML error pages dropped.
• WIKIJS_READ_ONLY=true does not register the write tools at all, and WIKIJS_DENY_TOOLS cuts finer along the same line — a filtered tool is never built, not refused at call time.

Releasing

1. Add the CHANGELOG entry and bump package.json.
2. npm run lint && npm run build && npm run test:coverage
3. Commit, then push a signed tag: git tag -s vX.Y.Z -m "vX.Y.Z" && git push origin main vX.Y.Z

The release workflow publishes to npm (Trusted Publishing, with provenance), creates the GitHub release from the CHANGELOG section and updates the MCP Registry entry.

License

MIT © Willi Thiel