Ask Claude about your own processes, decisions, and runbooks — not the internet's guess at them. Wikai's remote MCP server gives Claude Desktop your wiki as grounded context, scoped to one workspace.
Generate a token in Wikai (user menu → API tokens), then add this to claude_desktop_config.json (Settings → Developer → Edit Config; requires Node.js):
{
"mcpServers": {
"wikai": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://wikai.wiki/api/mcp",
"--header",
"Authorization: Bearer wk_YOUR_TOKEN"
]
}
}
}Claude Desktop's built-in remote-connector UI expects OAuth, which Wikai doesn't support yet — the mcp-remote bridge above is the reliable path today and carries your token in the Authorization header.
search_wiki returns real pages with ids, freshness, and snippets; get_page reads them in full — so Claude answers from what your team wrote and can point back to the exact page.
Tokens are scoped to one workspace, read-only unless you say otherwise, hashed at rest, and revocable instantly. Read tools ship readOnlyHint annotations.
On Pro and Ultra, a read + write token lets Claude file meeting notes or answers as new wiki pages — create-only, so it can never edit or delete existing ones.
Create a workspace, write a few pages, and connect Claude Desktop in minutes. Every plan can read over MCP; new workspaces start with a 14-day Pro trial, so agent writes work from day one.