Wiki.js

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.

What makes it different

Finds text search cannot. Wiki.js' default engine indexes titles and descriptions only — so search_pages says which engine is running, and grep_pages searches the actual text of pages.

Will not clobber a colleague. update_page compares against the moment you read the page and refuses to overwrite an edit saved in between. Surgical edits must match exactly once.

Writes can be confined to part of the wiki. WIKIJS_ALLOWED_PATHS limits the writing page and asset tools to path prefixes, matched by path segment, while reads stay unrestricted.

Requirements

• Node.js ≥ 24
• 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 — all six 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. That includes flush_page_cache, rebuild_page_tree and rebuild_search_index, which lose nothing but still act on the whole wiki.

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

Through mcp-hub

A client that cannot spawn a local process — ChatGPT connectors, Claude on the web, Cursor, LibreChat — reaches wikijs-mcp through mcp-hub: one container serves many stdio MCP servers over Streamable HTTP, with an OAuth 2.1 login behind a single password and long-lived tokens for the clients that cannot do OAuth. Its /hub endpoint puts every server behind six meta-tools, so one connector reaches all of them without N×tool schemas in the model's context, and it speaks both protocol revisions — a question this server asks travels through it to the person at the far end.

Its /config/mcp.json uses Claude Code's format, so the entry is the one you already have:

{

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

allowTools and denyTools there are the hub's own per-server filter, which is not the same thing as *_ALLOW_TOOLS in env — the difference, and the mistake it invites, are in the client guide.

Tools

62 tools. ★ marks the essential preset; ⚠ marks a tool that asks a person through MCP elicitation — a dialog the model cannot answer on its behalf, falling back to a two-call confirm_token where the client cannot show one. See Asking a person.

Every tool declares an outputSchema and answers with structuredContent alongside the text block, so a client can use the result without parsing prose. Twenty-nine tools that answered with a sentence — _"Deleted page 5 (path)."_ — now answer with the fields as well, and the sentence stays where a reader wants it.

The tools that report wiki content carry untrusted: true and source: "wikijs" as fields; page text, titles, descriptions and comments are written by anyone with edit rights. The list follows the call sites: a tool is marked exactly when it already routed its answer through the untrusted w