search_wiki_pagesLABSCO SUMMARY
Search first, then fetch the one page you want.
Worth knowing before you plan around it: the Wiki.JS GraphQL API has no native pagination, so paging is simulated on the client side, and neither search nor list results carry page bodies. Budget two calls — find the page, then fetch it by ID or path for the content.
What it is
A TypeScript MCP server that connects to your own Wiki.JS instance and lets an assistant find and read pages from it. It talks to the wiki's GraphQL endpoint and handles the query construction for you.
What you get
search_wiki_pages— keyword search with page and limit arguments for paging through resultslist_wiki_pages— a paginated listing of everything availableget_wiki_page— fetch one page by numeric ID or by path, and this is the call that returns full content- A connection test you can run before wiring it into a client
- Two run modes — stdio, or HTTP with a /health check and a /mcp endpoint
- A published Docker image with a healthcheck, and a compose example
Requirements
A running Wiki.JS instance and an API key whose permissions include page:read, page:list and search:read. Set WIKI_JS_BASE_URL and WIKI_JS_API_KEY, plus optional LOG_LEVEL, MCP_MODE and PORT — either in a .env file or as system environment variables. Install with npm, build, and start; or run the Docker image. MIT licensed.
Setup effort
Add the configuration to your client
USE CASES
01
Answering from your own documentation
Search on the topic, pick the best hit, then pull that page's full text into the conversation.
02
Seeing what documentation exists at all
Page through the full listing to get the shape of the wiki before you start searching it.
03
Wiring wiki lookup into an agent over HTTP
Run it in HTTP mode behind the health check and call the MCP endpoint from your own orchestration.
3 tools
Listed in project docs. Your client may show a different list.
list_wiki_pagesget_wiki_pageBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
- npx on PATH
- WIKI_JS_API_KEY in your environment
INSTALLATION
Connect your client
This one is configured rather than run — your client needs the configuration block, not a command.
Server setup
JSON
{
"mcpServers": {
"avr-docs-mcp": {
"command": "npx",
"args": [
"-y",
"avr-docs-mcp"
],
"env": {
"WIKI_JS_BASE_URL": "<YOUR_WIKI_JS_BASE_URL>",
"WIKI_JS_API_KEY": "<YOUR_WIKI_JS_API_KEY>"
}
}
}
}
