wiki-js

This MCP server provides integration between Wiki.js and an automated documentation workflow with hierarchical doc support. It exposes a set of Wiki.js specific MCP tools that can scan repositories, map code structures to wiki pages, create nested documentation, and synchronize changes back to Wiki.js. The server is designed to work with Cursor or similar AI-assisted IDEs, enabling you to automatically generate and maintain documentation across large codebases. Once the MCP server is running, you can query and invoke tools such as wikijs_create_repo_structure, wikijs_create_nested_page, wikijs_get_page, wikijs_sync_file_docs, and wikijs_repository_context to build a comprehensive, navigable documentation graph that mirrors your repository structure and code organization.

Prerequisites:

• Docker and Docker Compose installed on your machine
• Access to the internet from your build host
• Basic familiarity with Wiki.js and environment configuration

Installation steps:

1. Clone the MCP server repository and navigate into it
2. Copy the environment template and configure credentials:
   • cp config/example.env .env
   • Edit .env to set WIKIJS_TOKEN and any Wiki.js API credentials, plus any Wiki.js base URL if needed
   • Set POSTGRES_PASSWORD and other required environment variables as described in the .env template
3. Build and run the Docker-based MCP server:

   docker-compose -f docker.yml up -d
   

   This command brings up the Wiki.js instance (via Docker) and the MCP server wired to it
4. Initialize and test the MCP server:

   ./setup.sh
   # Optionally configure environment variables in .env as you go
   ./test-server.sh
   

5. Start the MCP server (live updates will appear in your Cursor interface after editing mcp.json):

   ./start-server.sh
   

6. Configure Cursor to connect to the MCP server by adding or updating your ~/.cursor/mcp.json with the server entry, for example:

   {
     "mcpServers": {
       "wikijs": {
         "command": "/path/to/wiki-js-mcp/start-server.sh"
       }
     }
   }
   

7. Open Wiki.js at http://localhost:3000 and complete the initial setup if prompted. Ensure the MCP server reports healthy status and the tools are listed in Cursor.

Tips and notes:

• Ensure WIKIJS_TOKEN in your .env is valid and has the necessary permissions to access and modify documentation via the Wiki.js API.
• The Docker-based setup persists data through volumes; use docker-compose down -v only if you intend to reset data.
• If the MCP tools do not appear in Cursor, refresh the MCP connection or restart the MCP server to re-populate the tool list.
• Review environment variables in .env for any Wiki.js base URL, API endpoints, or database configuration that may differ in development vs. production environments.
• For large repositories, the hierarchical documentation tools will help auto-generate and organize pages; monitor change tracking and mapping health via wikijs_connection_status and wikijs_repository_context.
• Common issues include API authentication failures, network access between the MCP container and Wiki.js, and mismatches in repository file paths used for auto-organization.