Wiki.js MCP Server

The Wiki.js MCP Server is a purpose‑built bridge that connects the rich, hierarchical knowledge base of Wiki.js to AI assistants via the Model Context Protocol. It addresses a common pain point in modern software teams: keeping documentation and source code tightly coupled while still allowing AI agents to query, update, and generate content on demand. By exposing a GraphQL‑powered API that mirrors the Wiki.js data model, the server lets developers treat documentation as first‑class citizens in their AI workflows.

At its core, the server translates file system events into structured documentation actions. When a new source file is added or an existing one is modified, the server can automatically create a corresponding Wiki.js page, establish parent‑child relationships, and embed code snippets directly into the documentation. This guarantees that every piece of code has an up‑to‑date reference, reducing knowledge drift and making onboarding easier. For large organizations managing multiple repositories, the hierarchical organization feature lets teams group docs by repository, component type, or business domain without manual effort.

Key capabilities include:

• Hierarchical Documentation Management – Create, update, and delete pages with nested relationships that reflect the actual code structure.
• Automated File‑to‑Page Mapping – The server parses source files to extract classes, functions, and dependencies, then maps those entities to Wiki.js pages.
• Bulk Operations & Change Tracking – Perform simultaneous updates across thousands of pages and monitor file modifications to trigger syncs automatically.
• GraphQL Compatibility – Full support for Wiki.js v2+ ensures seamless integration with existing installations and custom workflows.
• Docker‑Ready Deployment – A single file spins up Wiki.js, PostgreSQL, and the MCP server with persistent storage and health checks.

In practice, a development team can embed this server into an AI‑powered IDE such as Cursor. Global rules enforce that the assistant first searches existing documentation before suggesting code, automatically creates new pages for uncharted features, and keeps docs in sync with refactors. This workflow eliminates duplicate effort, preserves architectural consistency, and ensures that every code change is immediately reflected in the knowledge base. For organizations where documentation quality directly impacts product reliability, the Wiki.js MCP Server turns an often neglected asset into a dynamic, AI‑driven resource that scales with the codebase.