A comprehensive Model Context Protocol (MCP) server for Wiki.js integration with hierarchical documentation support and Docker deployment. Perfect for organizations managing multiple repositories and large-scale documentation.
First, clone this repository and set up environment variables:
# Copy environment template
cp config/example.env .env
# Edit .env with your credentials:
# - Set POSTGRES_PASSWORD to a secure password
# - Update other settings as needed# Start Wiki.js with Docker
docker-compose -f docker.yml up -dWiki.js will be available at http://localhost:3000
Complete the initial setup in the web interface
# Install Python dependencies
./setup.sh
# Update .env with Wiki.js API credentials:
# - Get API key from Wiki.js admin panel
# - Set WIKIJS_TOKEN in .env file
# Test the connection
./test-server.sh
# Start MCP server
# (not needed for AI IDEs like Cursor, simply click on the refresh icon after editing mcp.json
# and you should see a green dot with all tools listed. In existing open Cursor windows,
# this refresh is necessary in order to use this MCP)
./start-server.shAdd to your ~/.cursor/mcp.json:
{
"mcpServers": {
"wikijs": {
"command": "/path/to/wiki-js-mcp/start-server.sh"
}
}
}Add these Global Rules in Cursor to automatically leverage documentation before coding:
Before writing any code, always:
1. Search existing documentation using wikijs_search_pages to understand current patterns and architecture
2. Check for related components, functions, or modules that might already exist
3. If documentation exists for similar functionality, follow the established patterns and naming conventions
4. If no documentation exists, create it using wikijs_create_page or wikijs_create_nested_page before implementing
5. Always update documentation when making changes using wikijs_sync_file_docs
6. For new features, use wikijs_create_repo_structure to plan the documentation hierarchy first
These rules ensure that your AI assistant will:
- β Check documentation before suggesting implementations
- β Follow existing patterns and conventions
- β Maintain up-to-date documentation automatically
- β Create structured documentation for new features
- β Avoid duplicating existing functionality
# Before starting a new feature
"Search the documentation for authentication patterns before implementing login"
# When creating components
"Create nested documentation under frontend-app/components before building the React component"
# For API development
"Check existing API documentation and create endpoint docs using the established structure"
# During refactoring
"Update all related documentation pages for the files I'm about to modify"
- Repository-level organization: Create structured docs for multiple repos
- Nested page creation: Automatic parent-child relationships
- Auto-organization: Smart categorization by file type (components, API, utils, etc.)
- Enterprise scalability: Handle hundreds of repos and thousands of files
- GraphQL API integration: Full Wiki.js v2+ compatibility
- File-to-page mapping: Automatic linking between source code and documentation
- Code structure analysis: Extract classes, functions, and dependencies
- Bulk operations: Update multiple pages simultaneously
- Change tracking: Monitor file modifications and sync docs
- One-command deployment: Complete Wiki.js setup with PostgreSQL
- Persistent storage: Data survives container restarts
- Health checks: Automatic service monitoring
- Production-ready: Optimized for development and deployment
- Repository context detection: Auto-detect Git repositories
- Content generation: Auto-create documentation from code structure
- Search integration: Full-text search across hierarchical content
- Health monitoring: Connection status and error handling
wikijs_create_repo_structure- Create complete repository documentation structurewikijs_create_nested_page- Create pages with hierarchical pathswikijs_get_page_children- Navigate parent-child page relationshipswikijs_create_documentation_hierarchy- Auto-organize project files into docs
wikijs_create_page- Create new pages (now with parent support)wikijs_update_page- Update existing pageswikijs_get_page- Retrieve page content and metadatawikijs_search_pages- Search pages by text (fixed GraphQL issues)
wikijs_delete_page- Delete specific pages by ID or pathwikijs_batch_delete_pages- Batch delete with pattern matching and safety checkswikijs_delete_hierarchy- Delete entire page hierarchies with multiple modeswikijs_cleanup_orphaned_mappings- Clean up orphaned file-to-page mappings
wikijs_list_spaces- List top-level documentation spaceswikijs_create_space- Create new documentation spaceswikijs_manage_collections- Manage page collections
wikijs_link_file_to_page- Link source files to documentation pageswikijs_sync_file_docs- Sync code changes to documentationwikijs_generate_file_overview- Auto-generate file documentation
wikijs_bulk_update_project_docs- Batch update multiple pages
wikijs_connection_status- Check API connection healthwikijs_repository_context- Show repository mappings and context
Company Documentation/
βββ frontend-web-app/
β βββ Overview/
β βββ Components/
β β βββ Button/
β β βββ Modal/
β β βββ Form/
β βββ API Integration/
β βββ Deployment/
βββ backend-api/
β βββ Overview/
β βββ Controllers/
β βββ Models/
β βββ Database Schema/
βββ mobile-app/
β βββ Overview/
β βββ Screens/
β βββ Native Components/
βββ shared-libraries/
βββ UI Components/
βββ Utilities/
βββ Type Definitions/
The system intelligently categorizes files:
- Components: React/Vue components, UI elements
- API: Endpoints, controllers, routes
- Utils: Helper functions, utilities
- Services: Business logic, external integrations
- Models: Data models, types, schemas
- Tests: Unit tests, integration tests
- Config: Configuration files, environment setup
# Create complete repository structure
await wikijs_create_repo_structure(
"My Frontend App",
"Modern React application with TypeScript",
["Overview", "Components", "API", "Testing", "Deployment"]
)
# Create nested component documentation
await wikijs_create_nested_page(
"Button Component",
"# Button Component\n\nReusable button with multiple variants...",
"my-frontend-app/components"
)
# Auto-organize entire project
await wikijs_create_documentation_hierarchy(
"My Project",
[
{"file_path": "src/components/Button.tsx"},
{"file_path": "src/api/users.ts"},
{"file_path": "src/utils/helpers.ts"}
],
auto_organize=True
)# Clean up and manage documentation
# Preview what would be deleted (safe)
preview = await wikijs_delete_hierarchy(
"old-project",
delete_mode="include_root",
confirm_deletion=False
)
# Delete entire deprecated project
await wikijs_delete_hierarchy(
"old-project",
delete_mode="include_root",
confirm_deletion=True
)
# Batch delete test pages
await wikijs_batch_delete_pages(
path_pattern="*test*",
confirm_deletion=True
)
# Clean up orphaned file mappings
await wikijs_cleanup_orphaned_mappings()# Docker Database Configuration
POSTGRES_DB=wikijs
POSTGRES_USER=wikijs
POSTGRES_PASSWORD=your_secure_password_here
# Wiki.js Connection
WIKIJS_API_URL=http://localhost:3000
WIKIJS_API_KEY=your_jwt_token_here
# Alternative: Username/Password
WIKIJS_USERNAME=your_username
WIKIJS_PASSWORD=your_password
# Database & Logging
WIKIJS_MCP_DB=./wikijs_mappings.db
LOG_LEVEL=INFO
LOG_FILE=wikijs_mcp.log
# Repository Settings
REPOSITORY_ROOT=./
DEFAULT_SPACE_NAME=Documentation- JWT Token (Recommended): Use API key from Wiki.js admin panel
- Username/Password: Traditional login credentials
- Full GraphQL API support: Native Wiki.js v2+ compatibility
- Optimized queries: Efficient data fetching and mutations
- Error handling: Comprehensive GraphQL error management
- Retry logic: Automatic retry with exponential backoff
- SQLite storage: Local file-to-page mappings
- Repository context: Git repository detection and tracking
- Change tracking: File hash monitoring for sync detection
- Relationship management: Parent-child page hierarchies
- AST parsing: Extract Python classes, functions, imports
- Structure detection: Identify code patterns and organization
- Documentation generation: Auto-create comprehensive overviews
- Dependency mapping: Track imports and relationships
- Async operations: Non-blocking I/O for all API calls
- Bulk processing: Efficient batch operations for large projects
- Caching: Smart caching of page relationships and metadata
- Connection pooling: Optimized HTTP client management
wiki-js-mcp/
βββ src/
β βββ wiki_mcp_server.py # Main MCP server implementation
βββ config/
β βββ example.env # Configuration template
βββ docker.yml # Docker Compose setup
βββ pyproject.toml # Poetry dependencies
βββ requirements.txt # Pip dependencies
βββ setup.sh # Environment setup script
βββ start-server.sh # MCP server launcher
βββ test-server.sh # Interactive testing script
βββ HIERARCHICAL_FEATURES.md # Hierarchical documentation guide
βββ DELETION_TOOLS.md # Deletion and cleanup guide
βββ LICENSE # MIT License
βββ README.md # This file
- FastMCP: Official Python MCP SDK
- httpx: Async HTTP client for GraphQL
- SQLAlchemy: Database ORM for mappings
- Pydantic: Configuration and validation
- tenacity: Retry logic for reliability
# Check containers
docker-compose -f docker.yml ps
# View logs
docker-compose -f docker.yml logs wiki
docker-compose -f docker.yml logs postgres
# Reset everything
docker-compose -f docker.yml down -v
docker-compose -f docker.yml up -d# Check Wiki.js is running
curl http://localhost:3000/graphql
# Verify authentication
./test-server.sh
# Debug mode
export LOG_LEVEL=DEBUG
./start-server.sh- Port conflicts: Change port 3000 in
docker.ymlif needed - Database issues: Remove
postgres_data/and restart - API permissions: Ensure API key has admin privileges
- Python dependencies: Run
./setup.shto reinstall
- Hierarchical Features Guide - Complete guide to enterprise documentation
- Deletion Tools Guide - Comprehensive deletion and cleanup tools
- Configuration Examples - Environment setup
- Fork the repository
- Create feature branch (
git checkout -b feature/amazing-feature) - Commit changes (
git commit -m 'Add amazing feature') - Push to branch (
git push origin feature/amazing-feature) - Open Pull Request
This project is licensed under the MIT License - see the LICENSE file for details.
- Wiki.js Team: For the excellent documentation platform
- MCP Protocol: For the standardized AI integration framework
- FastMCP: For the Python MCP SDK
Ready to scale your documentation? π Start with wikijs_create_repo_structure and build enterprise-grade documentation hierarchies! Use the Cursor global rules to ensure documentation-first development! πβ¨