Provides tools for managing Wiki.js pages, including creating, updating, retrieving, listing, searching, deleting, and moving pages.
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-server Search wiki for pages about authentication."
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.
Claude Code plugin for Wiki.js integration — MCP server for page CRUD/search plus a docs-wiki skill that orchestrates documentation sub-agents to publish DE+EN docs.
Combines the previously separate wikijs-mcp-server (originally TypeScript, ported to Python here — see CHANGELOG) and mm-skills/docs-wiki into a single installable plugin, following the structure of mm-dev-toolkit and project-hub.
Related MCP server: wikijs-mcp-server
Install via the Claude Code plugin marketplace mechanism (marketplace add + plugin install), same as mm-dev-toolkit/project-hub. Then run /wikijs-plugin:setup — it creates a dedicated venv at ~/.wikijs-plugin/venv/ and copies the .env template.
Configure Wiki.js credentials in ~/.wikijs-plugin/.env:
WIKIJS_API_URL=https://your-wikijs-installation/graphql
WIKIJS_API_TOKEN=your-api-token-hereservers/wikijs-mcp-server/)Python (mcp[cli] + httpx), dedicated venv — same pattern as mm-dev-toolkit/project-hub.
Tool | Description |
| Create new wiki pages with Markdown or HTML |
| Update existing pages (content, title, tags) |
| Retrieve full page content and metadata |
| List pages with pagination and filtering |
| Full-text search across wiki pages |
| Permanently delete pages |
| Move pages to new paths |
| Read a page's logged change history (Phase 2, see below) |
| Record that a page was checked against the source code at a commit (local DB only) |
| Read the newest verified source ref per page and locale (local DB only) |
skills/docs-wiki/)/wikijs-plugin:docs-wiki — orchestrates documentation sub-agents (docs-architect, mermaid-expert, tutorial-engineer, api-documenter, reference-builder) to create/update Wiki.js pages in DE+EN.
skills/source-check/)/wikijs-plugin:source-check — checks the factual claims of a page (paths, class and method names,
config keys, commands, descriptions) against the project's source code. The README counts as a
claim, the code wins. docs-wiki runs it before translation-check and before every publish,
because an error that reads correctly and stands identically in DE and EN is invisible to the
translation check. /wikijs-plugin:source-check baseline checks all existing pages project by
project and reports findings without changing any page. Besides wrong claims it also reports what is
missing: an inventory built from the code (what the project itself defines for users: commands,
routes, config keys, environment variables, extension points, Twig hooks, entities, plus categories
per project type) is held against the whole page set, and anything that exists in the code but is
mentioned nowhere is listed as undocumented. That list is a note and never blocks a publish or the
verified marker. The full inventory runs for new docs, for pages without a verified ref and in the
baseline run; for pages with a verified ref an update checks only the delta of the changed files. The
inventory is heuristic, an empty result does not prove the page is complete, and
a "bewusst intern" decision is not stored, so the same items show up again on the next full run.
Verified state is stored in the local history DB and is per machine.
skills/translation-check/)/wikijs-plugin:translation-check — checks that DE (and optionally EN) page content reads
naturally instead of like a literal translation. docs-wiki runs it as a mandatory gate before
publishing: FAIL blocks the publish, WARN asks you, PASS continues. It uses a shipped glossary of
terms that stay as loanwords (e.g. "Cronjob"); add your own entries in
~/.wikijs-plugin/glossary.local.md (optional, takes precedence over the shipped glossary).
wikijs_create_page/wikijs_update_page accept optional sourceRepo/sourceRef/summary
parameters, logged to a local SQLite DB (~/.wikijs-plugin/wikijs-plugin.db) — never written
into the visible page content or description, so the project's "no version numbers in body text"
Wiki.js convention stays intact. docs-wiki passes the target project's git rev-parse HEAD as
sourceRef automatically when available. Read the log back with wikijs_get_page_history.
A logged sourceRef only means "written at". A page counts as verified once source-check passed
for it and wikijs_mark_verified recorded the ref together with the page's updatedAt; only that
verified ref serves as the baseline for diff-based updates, and only while the page still has that
updatedAt (an edit in the Wiki.js editor or outside docs-wiki makes it unverified again). Existing
refs from before this feature stay as information and are not verified. After updating the plugin, run
/wikijs-plugin:source-check baseline once, otherwise each page gets a full check on its first update.
Python 3.11+ (Windows: the py launcher works even where python/python3 are Microsoft Store alias stubs)
Wiki.js instance (v2.x or v3.x)
Wiki.js API token with page management permissions
See CONTRIBUTING.md.
PolyForm Noncommercial License 1.0.0 — source-available, personal and non-commercial use only. Not OSI Open Source. Commercial use requires explicit permission; contact the maintainer.
Markus Michalski
Website: markus-michalski.net
GitHub: @markus-michalski
Full Documentation (English)
Vollständige Dokumentation (Deutsch)
Original standalone TypeScript MCP server: wikijs-mcp-server
This server cannot be deployed
Shared project wiki for AI agents: read and write pages, next actions, and activity logs over MCP.
MCP-native open-source Notion alternative: read & write pages, databases and kanban boards.
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
The official MCP Server for the Mux API
