get_all_pages
Get all pages in WikiJS
LABSCO SUMMARY
Internal documentation becomes something an assistant can quote rather than something a person has to go and find.
Four tools, all of them reading: search when the page is unknown, path or ID when it is, and the full listing when the question is what exists at all. Locale is a parameter on both the search and the path lookup, which matters on a wiki carrying the same page in more than one language. Nothing writes, so the wiki cannot be changed from the conversation.
What it is
A read client for Wiki.js covering search, page retrieval and a full page listing.
What you get
- A search across pages by query string, narrowed by path and locale.
- A page fetched by its ID, or by its path and locale.
- Every page in the wiki listed.
Requirements
A Wiki.js instance at the address in WIKIJS_URL, and an API key in WIKIJS_API_KEY.
Setup effort
One command plus a key — npx -y wikijs-mcp, then supply credentials
USE CASES
01
Answering from internal documentation instead of from memory
Search finds the page and the path lookup returns it, so the answer can quote the wiki rather than approximate it.
02
Pulling a page whose location you already know
When the ID or the path is in hand, retrieval skips the search entirely.
03
Working out what documentation exists at all
The full listing answers the coverage question that a search cannot: what is written down, and what is not.
4 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_page_by_id
Get a WikiJS page by its ID
get_page_by_path
Get a WikiJS page by its path and locale
search_pages
Search for pages in WikiJS by query string
BEFORE YOU INSTALL
What to know first
Tools you get
4 tools when we connected. Read-only: the four tools search and retrieve pages, and none creates, updates or deletes one.
Requires
- npx on PATH
- A running Wiki.js instance, with its address in WIKIJS_URL
- WIKIJS_API_KEY in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y wikijs-mcpMCP Clients
Cursor — npx
CURSOR — NPX · JSON
{
"mcpServers": {
"wikijs-mcp": {
"command": "npx",
"args": [
"wikijs-mcp"
],
"env": {
"WIKIJS_URL": "<YOUR_WIKIJS_URL>",
"WIKIJS_API_KEY": "<YOUR_WIKIJS_API_KEY>"
}
}
}
}Cursor — HTTP
Start the server in HTTP mode
On the machine that will host it, with WIKIJS_URL and WIKIJS_API_KEY set in that shell (8080 is a port of your choice):
CURSOR — HTTP · TERMINAL
TRANSPORT_METHOD=streamable-http TRANSPORT_OPTIONS_PORT=8080 npx wikijs-mcpPoint Cursor at it
<YOUR_MCP_HOST_URL_PORT> is that machine's address and the port you chose, for example http://localhost:8080:
CURSOR — HTTP · JSON
{
"mcpServers": {
"wikijs-mcp": {
"name": "WikiJS MCP",
"url": "<YOUR_MCP_HOST_URL_PORT>/mcp"
}
}
}
