mcp-wikijs
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WIKIJS_URL | Yes | The URL of your Wiki.js instance | |
| WIKIJS_API_KEY | Yes | Your Wiki.js API key |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_pagesB | Search for pages in Wiki.js by keyword |
| get_pageB | Get the full content of a Wiki.js page by its path |
| list_pagesC | List all pages in Wiki.js |
| create_pageC | Create a new page in Wiki.js |
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
Each tool targets a unique operation on pages: create, get by path, list all, and search. No overlap in functionality.
All tools follow a consistent verb_noun pattern with snake_case (create_page, get_page, list_pages, search_pages).
With 4 tools, the set is well-scoped for basic page operations and within the ideal range of 3-15 tools.
Missing critical operations like update and delete pages, which are essential for a wiki. Agents cannot modify or remove pages, leading to workflow failures.