WikiJS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WIKIJS_URL | Yes | URL of your WikiJS instance | |
| WIKIJS_API_KEY | Yes | WikiJS API key | |
| TRANSPORT_METHOD | No | The transport method | stdio |
| TRANSPORT_OPTIONS_CORS_ORIGIN | No | Cors Origin (only on streamable-http) | * |
| TRANSPORT_OPTIONS_CORS_HEADERS | No | Cors Headers, comma separated (only on streamable-http) | Content-Type=mcp-session-id |
| TRANSPORT_OPTIONS_CORS_METHODS | No | Cors Methods, comma separated (only on streamable-http) | GET,POST,OPTIONS |
| TRANSPORT_OPTIONS_SESSION_TIMEOUT_MS | No | Session timeout (only on streamable-http) | 60000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_pagesC | Search for pages in WikiJS by query string |
| get_page_by_idC | Get a WikiJS page by its ID |
| get_page_by_pathB | Get a WikiJS page by its path and locale |
| get_all_pagesB | Get all pages in WikiJS |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.