wikijs-mcp
This is a Wiki.js MCP server that lets MCP clients search, read, and edit wiki content, and optionally manage assets, comments, users, groups, and maintenance jobs through 62 tools (or a curated 7-tool essential preset).
Search and browse pages with full-text search, regex content search, page listings, page trees, link graphs, and tag filters.
Read page metadata, outlines, source, rendered HTML, specific sections, and paged content windows.
Create, update, move, delete, and convert pages; apply surgical find-and-replace edits with concurrent-edit protection.
Inspect page history, compare versions, restore old versions, and resolve edit conflicts.
Manage tags, assets and asset folders, comments, users, groups, permissions, 2FA, activation, and password resets.
Inspect site info, locales, navigation, search engines, API keys, and storage targets; revoke API keys and toggle API access.
Run maintenance operations such as page rendering, cache flushing, page-tree rebuilds, search reindexing, history purging, and locale migration.
Apply safety controls including read-only mode, write path confinement, allow/deny tool filters, confirmation/elicitation gates, and untrusted-content marking.
Provides tools for interacting with Wiki.js, enabling search, read, and edit wiki pages, and optionally managing assets, comments, users, groups, and maintenance jobs through the Wiki.js GraphQL API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@wikijs-mcp search the wiki for the quarterly roadmap and summarize it"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Related MCP server: wikijs-mcp
Requirements
Node.js ≥ 24
A running Wiki.js instance and an API token
Configuration
Variable | Required | Description |
| yes | Base URL of the wiki, e.g. |
| yes | API key from Administration → API Access. |
| no | Locale assumed by page tools that are not given one (default |
| no |
|
| no | Comma-separated page path prefixes the write tools are confined to, e.g. |
| no | Comma-separated tool names, |
| no | Same syntax; removed from whatever |
| no |
|
| no |
|
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.
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_stateAn 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/notesMatching 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-mcpClaude 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-mcpThrough 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 wrapper.
update_page's stale-read refusal keeps its shape as a deliberate exception —
it stays an ordinary result rather than an error, because it is an instruction
for recovering rather than a failure, and it now says written: false with both
timestamps in fields.
Tool | Description |
| ★ Lists pages with their metadata, newest first by default. |
| ★ Reads one page, addressed by page_id or by path plus locale. |
| ★ Full-text search — but read this first: on a default Wiki.js the search engine is "Database - Basic", which only indexes page titles and descriptions, NOT the text inside pages. |
| ★ Searches the actual text of pages with a regular expression, by fetching them and matching locally. |
| ★ Lists the pages and folders directly under a path — the structural view a wiki has and a search does not. |
| Returns every page together with the internal links it contains — the wiki’s link graph for one locale. |
| ★ Creates a page. |
| ★ Changes a page. |
| Moves a page to another path, another locale, or both. |
| ⚠ Deletes a page and its history. |
| Changes the storage format of a page. |
| Lists the stored versions of a page, newest first, with who changed what and when. |
| Returns a single historical version of a page, including its full body as it was then. |
| Returns a unified diff between two versions of a page — or between one version and the page as it is now, if to_version is omitted. |
| Returns the version of a page that is newer than the one you read — what update_page points at when it refuses to write. |
| Rolls a page back to a stored version. |
| Every tag in the wiki, with its display title and when it was last used. |
| Finds tags matching a fragment. |
| Changes a tag’s name or display title across every page carrying it. |
| ⚠ Removes a tag from the wiki and from every page that carries it. |
| Lists the images and files in one asset folder. |
| Lists the folders directly under an asset folder. |
| Uploads an image or file to an asset folder, so it can be embedded in a page. |
| Creates a folder in the asset store. |
| Renames an asset. |
| ⚠ Deletes an asset permanently. |
| Returns the comments on one page, addressed by path and locale — not by page id, which is the one place Wiki.js asks for the path instead. |
| Returns a single comment by id, with its source and its rendered HTML. |
| Posts a comment on a page, optionally as a reply to another. |
| Replaces the body of a comment. |
| ⚠ Removes a comment permanently. |
| Lists the wiki’s user accounts. |
| Finds users by name or email. |
| Full detail for one account, including its group memberships and whether two-factor authentication is active. |
| Creates an account. |
| Changes an account’s details or its group membership. |
| ⚠ Removes an account. |
| Switches an account on or off. |
| Marks an account’s email as verified, which is otherwise done by the user clicking a link. |
| Switches an account’s second factor. |
| Starts Wiki.js’ own password reset for a local account, which emails the user a link. |
| Lists the wiki’s groups with how many users each has. |
| Returns one group with its global permissions, its page rules and its members. |
| Creates an empty group. |
| Replaces a group’s name, permissions and page rules wholesale — this is not a partial update, and omitting a rule deletes it. |
| ⚠ Removes a group. |
| Adds one account to one group, leaving its other memberships alone — the additive counterpart to update_user’s groups list. |
| Takes one account out of one group. |
| Version, database, host summary and the site’s own title and description, plus totals for pages, users, groups and tags. |
| Which locales are installed and which one is the default. |
| The sidebar navigation as configured, per locale. |
| Which search engine this wiki uses. |
| Lists the wiki’s API keys with their expiry and whether they are revoked, plus whether API access is switched on at all. |
| The configured storage backends — git mirrors, S3 buckets, local file dumps — with their sync status and last error. |
| ⚠ Revokes an API key immediately and for good — Wiki.js has no way to un-revoke one. |
| ⚠ Switches Wiki.js’ whole API on or off. |
| Forces Wiki.js to regenerate one page’s HTML from its source. |
| Drops Wiki.js’ rendered-page cache for the whole wiki. |
| Recomputes the folder structure Wiki.js derives from page paths. |
| Reindexes every page in the active search engine. |
| ⚠ Deletes stored page versions older than a cutoff, across the whole wiki. |
| ⚠ Moves all pages from one locale to another, across the whole wiki. |
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.
Not exposed, on purpose
No tool that creates an API key. Wiki.js can do it over GraphQL, and this server deliberately cannot: a model able to mint a full-access key could grant itself everything the three narrowing mechanisms above take away.
Reads are never path-scoped. WIKIJS_ALLOWED_PATHS confines writes only — a
scope on reads turns a wiki into a confusing half-wiki, and the key's own group
and page rules are the right place to hide pages, because they apply to
everything else using that key too.
Safety
Destructive and administrative tools ask a person. Where the client supports MCP elicitation they raise a real dialog that the model cannot answer on its behalf. Where it does not, the first call returns a short-lived token bound to the exact target and only a second call carrying it performs the operation — which proves the call was made twice with the same arguments and nothing more, and the text says so. The binding includes everything that decides what is touched — an approval for
migrate_pages_localefromdetoenwill not runentode.ELICITATION=falsetakes the fallback deliberately; it never removes the guard.Three maintenance tools are deliberately not gated.
flush_page_cache,rebuild_page_treeandrebuild_search_indexcost time, not content. A dialog in front of an operation that loses nothing is how people learn to tick without reading.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_keysandrevoke_api_keyare 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=truedoes not register the write tools at all, andWIKIJS_DENY_TOOLScuts finer along the same line — a filtered tool is never built, not refused at call time.
Documentation
The full guide, tool reference and security notes live at
wikijs-mcp.ni-c.de (source in docs/).
Development
npm install
npm run lint && npm run typecheck && npm run build && npm testThe unit suite drives the built server over the real MCP protocol against a fake
Wiki.js, so no instance is needed; npm run test:integration is the separate
suite that brings a real Wiki.js up in Docker and exercises every tool against it.
The architecture diagram and social card are generated — edit
docs/assets/architecture.source.svg and run npm run assets, never the rendered
copies — and npm run docs:tools regenerates the tool reference from the
catalogue.
Releasing
Add the CHANGELOG entry and bump
package.json.npm run lint && npm run build && npm run test:coverageCommit, 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.
Contributing
Issues, discussions and pull requests are welcome — see CONTRIBUTING.md. For vulnerabilities please use private reporting rather than a public issue; the policy is in SECURITY.md.
License
MIT © Willi Thiel
Available Tools
62 toolsassign_user_to_groupAdd a user to a groupAIdempotent
Adds one account to one group, leaving its other memberships alone — the additive counterpart to update_user’s groups list. Requires a confirmation token, because a group is what grants access.
Inputs: user_id (required), group_id (required), confirm_token. Returns: truncated
convert_page_editorConvert a page to another editorAIdempotent
Changes the storage format of a page. Wiki.js does not translate the body — converting markdown to "code" leaves the markdown source as raw HTML text. Use it to correct a page created with the wrong editor, not to reformat one.
Inputs: editor (required), path, locale, page_id, +1 more. Returns: truncated
create_asset_folderCreate an asset folderA
Creates a folder in the asset store. The slug is what appears in the URL of every file inside it.
Inputs: slug (required), name, parent_folder_id. Returns: truncated
create_commentPost a commentA
Posts a comment on a page, optionally as a reply to another. The comment is attributed to the account the API key belongs to, which is usually a service account rather than a person — say so in the text if that matters.
Inputs: content (required), page_id (required), reply_to. Returns: truncated
create_groupCreate a groupA
Creates an empty group. It starts with no permissions and no page rules, so it grants nothing until update_group is called.
Inputs: name (required). Returns: truncated
create_pageCreate a pageA
Creates a page. The path must not already exist in this locale — Wiki.js answers PageDuplicateCreate otherwise, and update_page is what changes an existing one. The editor decides how content is interpreted, so markdown source needs editor="markdown".
Inputs: path (required), title (required), content (required), tags, +5 more. Returns: truncated
create_userCreate a userA
Creates an account. For a local account supply a password, or set send_welcome_email so Wiki.js mails an invitation instead. Groups are given by id — list_groups has them, and an account in no group can log in but see nothing.
Inputs: name (required), email (required), groups, password, +4 more. Returns: truncated
delete_assetDelete a fileADestructiveIdempotent
Deletes an asset permanently. Any page embedding it will show a broken image or a dead link. Requires a confirmation token.
Inputs: asset_id (required), confirm_token. Returns: truncated
delete_commentDelete a commentADestructiveIdempotent
Removes a comment permanently. Replies to it are not removed with it. Requires a confirmation token.
Inputs: comment_id (required), confirm_token. Returns: truncated
delete_groupDelete a groupADestructiveIdempotent
Removes a group. Its members keep their accounts but lose whatever access the group gave them. Requires a confirmation token.
Inputs: group_id (required), confirm_token. Returns: truncated
delete_pageDelete a pageADestructiveIdempotent
Deletes a page and its history. Wiki.js has no trash — this cannot be undone from here. Requires a confirmation token.
Inputs: path, locale, page_id, confirm_token. Returns: truncated
delete_tagDelete a tagADestructiveIdempotent
Removes a tag from the wiki and from every page that carries it. The pages themselves are untouched. Requires a confirmation token.
Inputs: tag_id (required), confirm_token. Returns: truncated
delete_userDelete a userADestructiveIdempotent
Removes an account. Wiki.js needs somebody to inherit the pages it authored, so replace_with_user_id is required — pass the id of the account that should own them afterwards. Requires a confirmation token.
Inputs: user_id (required), replace_with_user_id (required), confirm_token. Returns: truncated
diff_page_versionsCompare two versionsARead-onlyIdempotent
Returns a unified diff between two versions of a page — or between one version and the page as it is now, if to_version is omitted. Answers "what changed here" in one call instead of two full page bodies.
Inputs: page_id (required), from_version (required), to_version, context_lines. Returns: source, truncated, untrusted
flush_page_cacheFlush the page cacheAIdempotent
Drops Wiki.js’ rendered-page cache for the whole wiki. Nothing is lost, but every page has to be rendered again on first access, so a busy instance gets slower for a while.
Inputs: no named parameters. Returns: truncated
get_commentGet one commentARead-onlyIdempotent
Returns a single comment by id, with its source and its rendered HTML.
Inputs: comment_id (required). Returns: source, truncated, untrusted
get_groupGet a groupARead-onlyIdempotent
Returns one group with its global permissions, its page rules and its members. This is the authoritative answer to "who can see or edit what" — and it is what update_group needs as its starting point, because that mutation replaces the whole rule set.
Inputs: group_id (required). Returns: source, truncated, untrusted
get_pageGet a pageARead-onlyIdempotent
Reads one page, addressed by page_id or by path plus locale. Choose a mode: "metadata" for everything but the text, "outline" for the headings only (cheapest way to see what a long page contains), "content" for the source, "rendered" for the HTML. With mode=content, either pass section to get one heading’s worth, or offset and max_chars to read the page in windows — a large page will otherwise be truncated to fit the result budget.
Inputs: mode, path, locale, offset, +3 more. Returns: source, truncated, untrusted
get_page_conflictGet the newer version behind a conflictARead-onlyIdempotent
Returns the version of a page that is newer than the one you read — what update_page points at when it refuses to write. Shows who saved it and when, so the change can be redone on top instead of discarded.
Inputs: page_id (required). Returns: source, truncated, untrusted
get_page_treeBrowse the page treeARead-onlyIdempotent
Lists the pages and folders directly under a path — the structural view a wiki has and a search does not. mode "ALL" returns both folders and pages, "FOLDERS" only folders, "PAGES" only pages. Wiki.js offers no limit on this query, so a very wide level is truncated to the result budget.
Inputs: mode, path, locale, include_ancestors. Returns: source, truncated, untrusted
get_page_versionGet one stored versionARead-onlyIdempotent
Returns a single historical version of a page, including its full body as it was then. To find out what changed between two versions, diff_page_versions is far cheaper than reading both.
Inputs: page_id (required), version_id (required). Returns: source, truncated, untrusted
get_site_infoGet site and system informationARead-onlyIdempotent
Version, database, host summary and the site’s own title and description, plus totals for pages, users, groups and tags. The first call to make when something is not behaving — it proves the URL and the API key work at all. Fields describing the host filesystem and database host are deliberately not requested.
Inputs: no named parameters. Returns: truncated
get_userGet a userARead-onlyIdempotent
Full detail for one account, including its group memberships and whether two-factor authentication is active. No credential of any kind is returned — Wiki.js does not expose one.
Inputs: user_id (required). Returns: source, truncated, untrusted
grep_pagesSearch inside page textARead-onlyIdempotent
Searches the actual text of pages with a regular expression, by fetching them and matching locally. This exists because Wiki.js’ default search engine does not index page content at all. It is the expensive path — one request per page — so narrow it with path_prefix, tags or locale, and keep max_pages small. Returns matching lines with context, not whole pages.
Inputs: pattern (required), tags, locale, max_pages, +3 more. Returns: source, truncated, untrusted
list_api_keysList API keysARead-onlyIdempotent
Lists the wiki’s API keys with their expiry and whether they are revoked, plus whether API access is switched on at all. Wiki.js stores only a truncated form of each key and never returns the secret, so nothing here can be used to authenticate.
Inputs: no named parameters. Returns: truncated
list_asset_foldersList asset foldersARead-onlyIdempotent
Lists the folders directly under an asset folder. Folder 0 is the root. Wiki.js returns one level at a time, so a deep tree needs one call per level.
Inputs: parent_folder_id. Returns: source, truncated, untrusted
list_assetsList assets in a folderARead-onlyIdempotent
Lists the images and files in one asset folder. Folder 0 is the root. Assets are flat within a folder and Wiki.js has no search across them, so finding one means walking list_asset_folders.
Inputs: kind, folder_id. Returns: source, truncated, untrusted
list_commentsList comments on a pageARead-onlyIdempotent
Returns the comments on one page, addressed by path and locale — not by page id, which is the one place Wiki.js asks for the path instead. An empty list can also mean comments are switched off for the wiki; get_site_info reports that.
Inputs: path (required), locale. Returns: source, truncated, untrusted
list_groupsList groupsARead-onlyIdempotent
Lists the wiki’s groups with how many users each has. Groups marked isSystem are Wiki.js’ own Administrators and Guests — they exist always and should not be deleted.
Inputs: filter, order_by. Returns: truncated
list_localesList localesARead-onlyIdempotent
Which locales are installed and which one is the default. Worth checking once per wiki: the locale is part of a page’s identity, and every page tool here falls back to WIKIJS_LOCALE, so a wiki running on "de" needs that set or nothing will be found.
Inputs: installed_only. Returns: truncated
list_page_historyList a page’s historyARead-onlyIdempotent
Lists the stored versions of a page, newest first, with who changed what and when. This is the one Wiki.js query that really paginates. The version ids here are what get_page_version, diff_page_versions and restore_page_version take.
Inputs: page, path, locale, page_id, +1 more. Returns: source, truncated, untrusted
list_page_linksList internal linksARead-onlyIdempotent
Returns every page together with the internal links it contains — the wiki’s link graph for one locale. Useful for finding what would break before moving or deleting a page. Wiki.js returns the whole graph at once and offers no filter, so on a large wiki this is truncated.
Inputs: locale. Returns: source, truncated, untrusted
list_pagesList pagesARead-onlyIdempotent
Lists pages with their metadata, newest first by default. The result reports how many pages matched as well as how many are shown, so a short answer is never mistaken for a small wiki. Wiki.js has no offset for this query, so narrow with tags, locale, creator_id or author_id rather than paging. Returns no page content; use get_page for that.
Inputs: tags, limit, locale, order_by, +3 more. Returns: source, truncated, untrusted
list_search_enginesList search enginesARead-onlyIdempotent
Which search engine this wiki uses. Worth knowing before trusting search_pages: the default "Database - Basic" indexes only titles and descriptions, so nothing written inside a page is searchable until a real engine is configured and the index rebuilt.
Inputs: no named parameters. Returns: truncated
list_storage_targetsList storage targetsARead-onlyIdempotent
The configured storage backends — git mirrors, S3 buckets, local file dumps — with their sync status and last error. Credentials in their configuration are redacted.
Inputs: no named parameters. Returns: truncated
list_tagsList all tagsARead-onlyIdempotent
Every tag in the wiki, with its display title and when it was last used. Tags are the one cross-cutting index a wiki has, so this is often a better starting point than search — feed a tag back into list_pages to see what carries it.
Inputs: no named parameters. Returns: source, truncated, untrusted
list_usersList usersARead-onlyIdempotent
Lists the wiki’s user accounts. providerKey says how they log in — "local" for a Wiki.js password, anything else for an identity provider. Email addresses are returned because they are the login.
Inputs: limit, filter, order_by. Returns: source, truncated, untrusted
migrate_pages_localeMove every page to another localeADestructiveIdempotent
Moves all pages from one locale to another, across the whole wiki. The usual reason is a wiki set up under the wrong locale code. Every page path changes, so every external link into the wiki breaks. Requires a confirmation token.
Inputs: source_locale (required), target_locale (required), confirm_token. Returns: truncated
move_pageMove or rename a pageAIdempotent
Moves a page to another path, another locale, or both. Internal links pointing at the old path are NOT rewritten by Wiki.js — check list_page_links first if that matters.
Inputs: destination_path (required), path, locale, page_id, +2 more. Returns: truncated
purge_page_historyPurge old page versionsADestructiveIdempotent
Deletes stored page versions older than a cutoff, across the whole wiki. The versions are gone permanently — this is the one maintenance operation that destroys data. Requires a confirmation token.
Inputs: older_than (required), confirm_token. Returns: truncated
rebuild_page_treeRebuild the page treeAIdempotent
Recomputes the folder structure Wiki.js derives from page paths. The repair for a navigation tree that disagrees with the pages actually present, usually after a bulk import or a database edit. Page content is untouched, but it walks every page and can take minutes.
Inputs: no named parameters. Returns: truncated
rebuild_search_indexRebuild the search indexAIdempotent
Reindexes every page in the active search engine. Required once after switching away from "Database - Basic", because the new engine starts empty and search silently returns nothing until this runs. On the basic engine it does nothing. Search results may be incomplete while it runs, and it can take minutes on a large wiki.
Inputs: no named parameters. Returns: truncated
rename_assetRename a fileAIdempotent
Renames an asset. Pages embedding it by its old URL will break — Wiki.js does not rewrite them.
Inputs: asset_id (required), filename (required), confirm_token. Returns: truncated
render_pageRe-render a pageAIdempotent
Forces Wiki.js to regenerate one page’s HTML from its source. The fix for a page whose rendering is stale after a theme or renderer change. Changes no content and cannot lose anything.
It does, however, bump the page’s updatedAt — and update_page compares that against when you last read the page, to catch somebody else saving in between. So a render between your read and your write makes update_page refuse your own next write, saying the page changed after you read it. If that happens, call get_page again and then write; nothing was lost. Better still, render after writing rather than before.
Inputs: page_id (required). Returns: truncated
reset_user_passwordReset a user’s passwordADestructiveIdempotent
Starts Wiki.js’ own password reset for a local account, which emails the user a link. No password is chosen or returned here. Requires a confirmation token.
Inputs: user_id (required), confirm_token. Returns: truncated
restore_page_versionRestore an earlier versionADestructiveIdempotent
Rolls a page back to a stored version. The current content is not lost — it becomes another entry in the history — but the live page is replaced. Requires a confirmation token.
Inputs: page_id (required), version_id (required), confirm_token. Returns: truncated
revoke_api_keyRevoke an API keyADestructiveIdempotent
Revokes an API key immediately and for good — Wiki.js has no way to un-revoke one. Note that this can revoke the key this server is using, which would cut its own connection. Requires a confirmation token.
Inputs: key_id (required), confirm_token. Returns: truncated
search_pagesSearch pagesARead-onlyIdempotent
Full-text search — but read this first: on a default Wiki.js the search engine is "Database - Basic", which only indexes page titles and descriptions, NOT the text inside pages. The result names the active engine so you can tell. If the engine is basic and you are looking for something written inside a page, use grep_pages instead. Results carry no excerpt; follow up with get_page.
Inputs: query (required), path, limit, locale. Returns: source, truncated, untrusted
search_tagsSearch tagsARead-onlyIdempotent
Finds tags matching a fragment. Cheaper than list_tags on a wiki with hundreds of them, and the usual way to check what a tag is actually called before filtering list_pages by it.
Inputs: query (required). Returns: source, truncated, untrusted
search_usersSearch usersARead-onlyIdempotent
Finds users by name or email. Use it to resolve a person to the id that list_pages (creator_id, author_id) and the group tools take.
Inputs: query (required). Returns: source, truncated, untrusted
set_api_stateTurn the API on or offADestructiveIdempotent
Switches Wiki.js’ whole API on or off. Turning it off disables every API key at once, including this server’s — after which the only way back is the web administration UI. Requires a confirmation token.
Inputs: enabled (required), confirm_token. Returns: truncated
set_user_activeActivate or deactivate a userAIdempotent
Switches an account on or off. A deactivated account keeps its pages and groups but cannot sign in — the reversible alternative to delete_user. Requires a confirmation token.
Inputs: active (required), user_id (required), confirm_token. Returns: truncated
set_user_tfaTurn two-factor authentication on or offAIdempotent
Switches an account’s second factor. Turning it OFF weakens that account and is the reason this is gated; turning it on forces the user to enrol at their next sign-in. Requires a confirmation token.
Inputs: enabled (required), user_id (required), confirm_token. Returns: truncated
unassign_user_from_groupRemove a user from a groupADestructiveIdempotent
Takes one account out of one group. Requires a confirmation token — removing somebody from their only group leaves them able to sign in and see nothing.
Inputs: user_id (required), group_id (required), confirm_token. Returns: truncated
update_commentEdit a commentADestructiveIdempotent
Replaces the body of a comment. Wiki.js keeps no history for comments, so the previous text is gone.
Inputs: content (required), comment_id (required), confirm_token. Returns: truncated
update_groupUpdate a group’s permissionsADestructiveIdempotent
Replaces a group’s name, permissions, page rules and login redirect wholesale — this is not a partial update, and omitting a rule deletes it, just as omitting redirect_on_login resets it to "/". Read the group with get_group first and send back the full set with your change applied. Requires a confirmation token, because this is the call that decides who can read and edit the wiki.
Inputs: name (required), group_id (required), page_rules (required), permissions (required), +2 more. Returns: truncated
update_pageUpdate a pageA
Changes a page. Pass content to replace the whole body, or edits for surgical find-and-replace — each edit’s old_text must appear exactly once, and an ambiguous or missing match is refused rather than applied to the wrong place. Before writing, this checks whether somebody else changed the page since it was read and refuses to clobber them; pass force=true to overwrite deliberately. Metadata fields can be changed on their own, without touching the text.
That refusal is a normal result and not an error: it explains what to do — read the page again with get_page, redo the change on top of what is now there, and write. Note that render_page also bumps the page’s timestamp, so calling it between your read and your write triggers the same refusal even though nobody else touched anything.
Inputs: path, tags, edits, force, +9 more. Returns: truncated
update_tagRename a tagADestructiveIdempotent
Changes a tag’s name or display title across every page carrying it. Renaming affects all of them at once, which is the point and also the risk, so it needs a confirmation token.
Inputs: tag (required), title (required), tag_id (required), confirm_token. Returns: truncated
update_userUpdate a userADestructiveIdempotent
Changes an account’s details or its group membership. The groups list replaces the existing one rather than adding to it — use assign_user_to_group for a single addition.
Inputs: user_id (required), name, email, groups, +3 more. Returns: truncated
upload_assetUpload a fileA
Uploads an image or file to an asset folder, so it can be embedded in a page. Content is passed base64-encoded and the content type is derived from the extension. SVG, HTML and XML are refused: Wiki.js serves assets from the wiki’s own origin, so those can carry script that runs for every reader. Note that Wiki.js 2.x has no GraphQL mutation for uploads at all — this uses the editor’s own route, which is undocumented and could change in a future Wiki.js release.
Inputs: filename (required), content_base64 (required), folder_id. Returns: truncated
verify_userMark a user as verifiedAIdempotent
Marks an account’s email as verified, which is otherwise done by the user clicking a link. Requires a confirmation token.
Inputs: user_id (required), confirm_token. Returns: truncated
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 62 tools
Each tool pairs a clear resource (page, tag, asset, comment, user, group, site) with a distinct action, and near-overlapping pairs like search_pages/grep_pages or get_page_tree/get_navigation_tree are explicitly differentiated in their descriptions. An agent can reliably tell which tool to call.
Tools consistently use snake_case verb_noun names: list_* for collections, get_* for single entities, create_*/update_*/delete_* for CRUD, and domain-specific verbs like move/restore/assign/rebuild. Even unusual names like grep_pages or convert_page_editor follow the same pattern.
62 tools far exceeds the 50+ threshold and would impose a heavy context and selection burden on an agent. The set is comprehensive, but this is a kitchen-sink Wiki.js admin API rather than a well-scoped MCP server; splitting it into page, user, asset, and system servers would be better.
The surface provides strong lifecycle coverage for pages, comments, users, and groups, including history, versions, search, and maintenance operations. Minor gaps remain: assets have upload/rename/delete but no download/read tool, asset folders cannot be deleted, and navigation can be read but not edited.
Maintenance
Related MCP Connectors
Search and manage your team's knowledge from MCP clients.
Connect to your MediaWiki using simple credentials and manage content without OAuth. Search, read,…
Read and write your team's shared, AI-readable wiki from any MCP client.
Shared project wiki for AI agents: read and write pages, next actions, and activity logs over MCP.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for accessing Wiki.js through its GraphQL API, enabling page management, search, tags, and system info operations.MIT
- AlicenseAqualityDmaintenanceAn MCP server for managing Wiki.js 2.x pages through its GraphQL API, enabling search, read, create, update, move, delete, version history, and asset listing.1342 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for interacting with Wiki.js via GraphQL API, enabling page management (CRUD, search, publish), user and group management, and blogging workflow with drafts.23 npmMIT
- FlicenseNot gradedqualityBmaintenanceMCP server for Wiki.js integration, enabling page CRUD operations (create, update, get, list, search, delete, move) via the Wiki.js GraphQL API.-