Connect your tool

WikiAIG speaks MCP. Any MCP-aware client can read your wikis and write to them. This page covers the four most common clients — Claude Code, Cursor, Codex CLI, Claude Desktop — and "any other MCP client" at the bottom.

The pattern is always the same: get a connection string from WikiAIG, paste it into your tool's MCP config, restart the tool. Reading is anonymous for public wikis. Writing — or reading private wikis — needs a token.

Get your connection details

On any wiki page in WikiAIG, click Connect → Copy endpoint. You'll get two things:

• The MCP endpoint URL — looks like https://www.wikiaig.com/mcp/<wiki-slug>
• Optionally, a write token if you want the client to push content back. Generate one from Settings → Tokens. Treat it like any other API key.

For multi-wiki access from one client, use your account-level endpoint instead of a per-wiki one. The client sees every wiki you own plus any public wikis on the platform.

Claude Code

Add to your ~/.config/claude-code/mcp.json or via the in-app MCP settings panel:

{
  "mcpServers": {
    "wikiaig": {
      "url": "https://www.wikiaig.com/mcp/your-wiki-slug",
      "headers": {
        "Authorization": "Bearer ${WIKIAIG_TOKEN}"
      }
    }
  }
}

Set WIKIAIG_TOKEN in your environment. Restart Claude Code. The wiki tools (search_wiki, read_page, write_page) appear in the tool list.

For read-only access to public wikis, omit the headers block entirely.

Cursor

Cursor uses the same MCP config format. Open the command palette → MCP Servers → Edit configuration and add:

{
  "wikiaig": {
    "url": "https://www.wikiaig.com/mcp/your-wiki-slug",
    "headers": { "Authorization": "Bearer YOUR_TOKEN" }
  }
}

Restart Cursor. Wiki tools show up in the agent's tool list automatically.

Codex CLI

Codex CLI reads MCP servers from ~/.codex/config.toml:

[mcp_servers.wikiaig]
url = "https://www.wikiaig.com/mcp/your-wiki-slug"

[mcp_servers.wikiaig.headers]
Authorization = "Bearer ${WIKIAIG_TOKEN}"

Then codex picks it up on next launch.

Claude Desktop

Open Settings → Developer → Edit Config and add the same mcpServers block as Claude Code. Restart the app.

For Desktop specifically, watch for the MCP indicator in the chat input — it'll show your connected servers and tool count.

Any other MCP client

If your tool supports MCP, it'll accept the same connection URL. WikiAIG implements the standard MCP transports, so most modern MCP clients work without configuration tricks.

If you hit a problem, the [Pushing content via MCP](pushing-content-via-mcp) page covers the developer workflow including the write tools.

Verifying it works

After restart, ask your tool to read the wiki:

"What pages are in my WikiAIG wiki?"

If it returns a list, you're connected. If it doesn't, check:

1. Token is set and not expired (Settings → Tokens shows last-used timestamps)
2. The endpoint URL matches the wiki slug exactly (no trailing slash, no /page-name)
3. The tool was fully restarted, not just reloaded

What's next

→ [Pushing content via MCP](pushing-content-via-mcp) — the developer workflow for writing pages from your AI tool.