An MCP server that connects MCP clients to your Wiki.js instance.
It supports both local connections over stdio and remote connections using the official MCP Streamable HTTP transport, making it suitable for local MCP clients as well as remotely hosted clients.
Prerequisites
MCP server designed to connect Claude Code to a Wiki.js instance
Python 3.10+
A Wiki.js instance with API access enabled
A Wiki.js API key (Administration > API Access > New API Key)
Installation
pip install wikijs-mcp
For local development:
git clone https://github.com/Ho3pLi/wikijs-mcp-http.git
cd wikijs-mcp-http
pip install -e .
Configuration
Wiki.js
Variable
Default
Description
WIKIJS_URL
required
Base URL of your Wiki.js instance
WIKIJS_API_KEY
required for stdio/single-key mode
Legacy/default Wiki.js API key. Kept server-side and never returned by tools
WIKIJS_GRAPHQL_ENDPOINT
/graphql
Wiki.js GraphQL endpoint path
WIKIJS_READ_ONLY
false
When true, mutation tools are disabled
Variable
Default
Description
-------------------------
----------
----------------------------------------
WIKIJS_URL
required
Base URL of your Wiki.js instance
WIKIJS_API_KEY
required
Wiki.js API key
WIKIJS_GRAPHQL_ENDPOINT
/graphql
Wiki.js GraphQL endpoint path
WIKIJS_READ_ONLY
false
When true, mutation tools are disabled
The Wiki.js API key is used only by the MCP server to communicate with Wiki.js. It remains server-side and is never returned or exposed to MCP clients.
Streamable HTTP
Variable
Default
Description
MCP_HOST
127.0.0.1
Host interface for HTTP mode
MCP_PORT
8000
Port for HTTP mode
MCP_PATH
/mcp
MCP Streamable HTTP endpoint path
MCP_ALLOWED_HOSTS
127.0.0.1:*,localhost:*
Comma-separated Host header allowlist
MCP_ALLOWED_ORIGINS
http://127.0.0.1:*,http://localhost:*
Comma-separated Origin header allowlist
Cloudflare Access multi-user authorization, for remote Streamable HTTP deployments:
Variable
Default
Description
WIKIJS_CF_ACCESS_ISSUER
unset
Cloudflare Access JWT issuer, usually https://<team-name>.cloudflareaccess.com
WIKIJS_CF_ACCESS_AUDIENCE
unset
Cloudflare Access application audience tag
WIKIJS_CF_ACCESS_JWKS_URL
unset
Cloudflare Access JWKS URL, usually https://<team-name>.cloudflareaccess.com/cdn-cgi/access/certs
WIKIJS_AUTH_USERS
unset
User email to credential profile mapping
WIKIJS_AUTH_PROFILES
unset
Credential profile to Wiki.js API-key environment variable mapping
The server does not bind to 0.0.0.0 by default. For production, put HTTPS/authentication in front of the local HTTP listener.
The server intentionally does not bind to 0.0.0.0 by default.
For remote deployments, the recommended setup is to keep the MCP server listening locally and expose it through an HTTPS reverse proxy and, when appropriate, an authentication layer.
Choosing a transport
WikiJS MCP supports two MCP transports.
stdio
Use stdio when the MCP client can start the MCP server locally.
This is typically the simplest option for local clients such as Claude Code or other desktop/development tools.
The MCP Python SDK enforces DNS rebinding protection for HTTP transports.
Cloudflare Access multi-user mode
By default, both stdio and Streamable HTTP use the single WIKIJS_API_KEY.
For a remote MCP protected by Cloudflare Access, you can enable multi-user mode. The server validates the Cf-Access-Jwt-Assertion header, extracts the authenticated email, maps it to a credential profile, then uses the Wiki.js API key from that profile only for the current MCP request. It does not mutate the global config or reuse a client with a changed authorization header.
Do not put Wiki.js API keys directly in WIKIJS_AUTH_USERS or WIKIJS_AUTH_PROFILES; profiles reference environment variable names only. Multiple users can share one profile, and the Wiki.js API key assigned to that profile should be associated with the corresponding Wiki.js group. Wiki.js remains the source of truth for page permissions and Page Rules.
When multi-user mode is configured in Streamable HTTP mode:
Missing or invalid Cf-Access-Jwt-Assertion is rejected.
Expired assertions, wrong issuer, and wrong audience are rejected.
Authenticated users without a mapping are rejected.
Missing profile definitions or missing API-key environment variables are rejected.
The server does not fall back to WIKIJS_API_KEY for remote authenticated requests.
In stdio, local use remains unchanged and uses WIKIJS_API_KEY.
In Cloudflare, the Access application audience tag is visible in the Access application settings. The issuer and JWKS URL are based on your team domain:
Authentication and access control should normally be handled in front of the MCP server when exposing it publicly.
For example, an identity-aware proxy, OAuth-capable gateway, VPN, or equivalent access-control layer can sit between the remote MCP client and nginx/MCP endpoint.
Read-only mode
WikiJS MCP can expose Wiki.js content without allowing clients to modify it.
Списка инструментов пока нет. У удалённых серверов он появляется после первой проверки состояния.
FAQ
Вопросы
Как установить Wikijs?
Скопируйте на этой странице конфигурацию stdio для Cursor, Claude Desktop, Claude Code или VS Code. Она использует установку издателя, а не прокси PlugMCP.
Нужен ли API-ключ для Wikijs?
В этой записи не указано обязательных переменных окружения.
Какой транспорт использует Wikijs?
Wikijs работает локально через stdio.
Когда Wikijs проверялся в последний раз?
Последняя проверка: 2026-10-28. MCP server designed to connect Claude Code to a Wiki.js instance