Wikai

Connect Cursor to your team wiki

Cursor writes better code when it knows your team's conventions, runbooks, and decisions. Wikai's remote MCP server serves your wiki as grounded context — one JSON snippet, nothing to host.

Connect with one config

Generate a token in Wikai (user menu → API tokens), then add the server to .cursor/mcp.json in your project — or ~/.cursor/mcp.json to use it everywhere:

{
  "mcpServers": {
    "wikai": {
      "url": "https://wikai.wiki/api/mcp",
      "headers": {
        "Authorization": "Bearer wk_YOUR_TOKEN"
      }
    }
  }
}
Grounded answers, citable pages

search_wiki returns real pages with ids, freshness, and snippets; get_page reads them in full — so Cursor answers from what your team wrote and can point back to the exact page.

Read-only by default

Tokens are scoped to one workspace, read-only unless you say otherwise, hashed at rest, and revocable instantly. Read tools ship readOnlyHint annotations.

Agents can write back

On Pro and Ultra, a read + write token lets Cursor file what it learns as new wiki pages — create-only, so it can never edit or delete existing ones.

How it works

  • 1.Generate a token. In Wikai, open API tokens from the user menu and generate a workspace-scoped token (wk_...). It's read-only by default — choose read + write only for agents you trust to add pages.
  • 2.Add the server to Cursor. Use the connect snippet above. The endpoint is https://wikai.wiki/api/mcp over Streamable HTTP — no install on our side, nothing to host on yours.
  • 3.Work with your wiki in reach. Cursor can now search your pages, read them in full, and see how the wiki is organized. On Pro and Ultra, a write token also lets it file new pages.
Free to start

Give Cursoryour team's context

Create a workspace, write a few pages, and connect Cursor in minutes. Every plan can read over MCP; new workspaces start with a 14-day Pro trial, so agent writes work from day one.

Start freeRead the full setup docs