This WikiJS MCP server enables AI assistants to interact with WikiJS knowledge bases by providing four key capabilities:
Search pages: Find WikiJS pages using query strings with optional path and locale filters
Get page by ID: Retrieve specific pages using their unique identifiers
Get page by path and locale: Fetch pages by specifying their path and locale
Get all pages: Retrieve a complete list of all pages in the WikiJS instance
This integration allows seamless search, retrieval, and listing of WikiJS content for AI-powered knowledge management.
Enables deployment of a WikiJS instance for testing through Docker Compose.
Used for configuration management through environment variables, allowing users to set required WikiJS URL and API key values.
Provides access to the repository for cloning and development purposes.
Optional build tool for compiling the project.
Package manager used to install dependencies and run the MCP server.
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 for articles about API documentation"
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.
A Model Context Protocol (MCP) server that provides integration with WikiJS, allowing AI assistants to search and retrieve content from your WikiJS knowledge base.
This MCP server enables AI assistants to interact with WikiJS instances by providing tools to:
Search for pages by query string
Retrieve pages by ID
Retrieve pages by path and locale
Get all pages from the wiki
Related MCP server: WikiJS MCP Server
{
"mcpServers": {
"wikijs-mcp": {
"command": "npx",
"args": [
"wikijs-mcp"
],
"env": {
"WIKIJS_URL": <your wikijs url>,
"WIKIJS_API_KEY": <your wikijs api key>
}
}
}
}Start the server TRANSPORT_METHOD=streamable-http TRANSPORT_OPTIONS_PORT=8080 npx wikijs-mcp (See Environment Variables for all available variables)
{
"mcpServers": {
"wikijs-mcp": {
"transport": "http-streamable",
"name": "WikiJS MCP",
"url": <your mcp host url with port>/mcp
}
}
}Log into your WikiJS instance as an administrator
Go to Administration > API Access
Create a new API key with appropriate permissions
Copy the generated key to your .env file
Clone the repository:
git clone https://github.com/RicardoCenci/wikijs-mcp.git
cd wikijs-mcpInstall dependencies:
npm installCopy the environment template and fill out its contents
cp env.example .envBuild the project
If you have make installed:
make buildDeploy the WikiJS instance for testing
docker compose up -dnpx wikijs-mcpVariable | Description | Required | Allowed Values | Default |
| URL of your WikiJS instance | Yes | - | - |
| WikiJS API key | Yes | - | - |
| The transport method | No | stdio, streamable-http | stdio |
| Cors Origin (only on streamable-http) | No | - | * |
| Cors Headers, comma separated (only on streamable-http) | No | - | Content-Type=mcp-session-id |
| Cors Methods, comma separated (only on streamable-http) | No | - | GET,POST,OPTIONS |
| Session timeout (only on streamable-http) | No | - | 60000 |
This project is licensed under the MIT License.
Get all pages in WikiJS
Inputs: no named parameters.
Get a WikiJS page by its ID
Inputs: id (required).
Get a WikiJS page by its path and locale
Inputs: locale (required), path (required).
Search for pages in WikiJS by query string
Inputs: query (required), locale, path.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 4 tools
The tools are mostly distinct, focusing on different retrieval methods for WikiJS pages. However, get_page_by_id and get_page_by_path could potentially be confused if an agent doesn't understand the difference between ID-based and path-based lookup, though their descriptions clarify this distinction.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_all_pages, search_pages). The naming is predictable and uniform throughout the set, making it easy for agents to understand the pattern.
With only 4 tools, the server feels thin for a WikiJS management system. While the tools cover basic retrieval and search, there are no tools for creating, updating, or deleting pages, which are essential operations for a wiki. The count is borderline for the apparent scope.
The tool set is severely incomplete for a WikiJS server. It only provides read-only operations (get and search), with no coverage for creating, updating, or deleting pages. This creates significant gaps that will cause agent failures when trying to perform full wiki management tasks.
Search your knowledge bases from any AI assistant using hybrid RAG.
Gives AI assistants read access to your Dedox help centre and knowledge base articles.
Shared knowledge base for AI agents. Semantic search across agents, no setup required — just a URL.
Search, read and save your Linko notes and resources (AI knowledge base) from any AI chat.
