Search, read and edit Wiki.js pages, and manage its assets, users, groups and comments
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
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.
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.
| Variable | Required | Description |
|---|---|---|
WIKIJS_URL | yes | Base URL of the wiki, e.g. https://wiki.example.com. A trailing /graphql is trimmed |
WIKIJS_TOKEN | yes | API key from Administration β API Access. WIKIJS_API_KEY is accepted as an alias |
WIKIJS_LOCALE | no | Locale assumed by page tools that are not given one (default en) |
WIKIJS_READ_ONLY | no | true, 1 or yes registers only the read tools |
WIKIJS_ALLOWED_PATHS | no | Comma-separated page path prefixes the write tools are confined to, e.g. docs,team/notes |
WIKIJS_ALLOW_TOOLS | no | Comma-separated tool names, list_* prefixes, or essential for a curated preset |
WIKIJS_DENY_TOOLS | no | Same syntax; removed from whatever WIKIJS_ALLOW_TOOLS left |
ELICITATION | no | false replaces the approval dialog with the two-call token. Not prefixed |
WIKIJS_INSECURE_TLS | no | true accepts self-signed certificates (scoped to this connection) |
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 overWIKIJS_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.
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.
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.
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.
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.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/wiki-js)<a href="https://allmcps.com/mcp/wiki-js"><img src="https://allmcps.com/api/badge/wiki-js?style=directory" alt="Wiki.js on AllMCPs" /></a>