Connect your Perfect Wiki knowledgebase to Claude, ChatGPT and other MCP-compatible AI assistants via the Perfect Wiki MCP server. Once connected, your assistant can read, search, and manage pages in your knowledgebase directly from the chat.
The MCP server endpoint is:
https://api.perfectwiki.xyz/mcpTwo ways to authenticate
- ✨ OAuth sign-in (new, recommended) — connect by signing in with your Perfect Wiki account. During the connection you choose which knowledgebase to expose and which permissions to grant (read-only or read & write). No tokens to copy, and you can revoke access at any time. This is how Claude (web, desktop, mobile) and ChatGPT connect.
- Static API token (legacy) — a Bearer token generated in Perfect Wiki settings, pasted into your client's MCP configuration. Still fully supported and useful for CLI tools, scripts and clients without OAuth support, but we recommend OAuth wherever it is available.
Claude (web, desktop and mobile) — via OAuth
- In Claude, open Settings → Connectors and click Add custom connector.
- Enter the URL https://api.perfectwiki.xyz/mcp. Leave Client ID and Client Secret blank — the connector registers itself automatically.
- Click Add, then Connect. A Perfect Wiki window opens: sign in (if you aren't already), choose the knowledgebase you want to connect, and click Allow access.
- Enable the connector in a chat via the tools menu. Connectors added on claude.ai automatically become available in the Claude desktop and mobile apps too.
ChatGPT (Developer Mode) — via OAuth
- In ChatGPT, enable connector support: Settings → Connectors → Advanced → Developer mode.
- Add a new connector with the server URL https://api.perfectwiki.xyz/mcp and choose OAuth as the authentication method.
- ChatGPT opens the Perfect Wiki sign-in and consent screen — pick your knowledgebase and approve access.
- Enable the connector in a conversation to use the tools.
Claude Code
With OAuth (recommended):
claude mcp add --transport http -s user perfect-wiki https://api.perfectwiki.xyz/mcpThen run /mcp inside Claude Code and follow the browser sign-in to authorize the connection.
With a legacy API token:
claude mcp add --transport http -s user perfect-wiki https://api.perfectwiki.xyz/mcp \
--header "Authorization: Bearer your-api-token"Tip: the -s (--scope) flag controls where the server configuration (including your API token) is stored:
- -s local (default) — saved to the current project only. Good if the token should not leave this project.
- -s user — saved to your user-level Claude config (~/.claude.json), so the server is available across all your projects on this machine. Recommended if you want to configure it once and reuse it everywhere.
- -s project — saved to .mcp.json in the project and checked into git. Avoid this for tokens, since the file is shared with your team.
Permissions and knowledgebase selection (OAuth)
When you connect via OAuth, you grant permissions on the consent screen:
- wiki:read — list pages, read page content, and ask AI-powered questions
- wiki:write — create, update and delete pages
Each OAuth connection is tied to one knowledgebase — the one you pick on the consent screen. To work with several knowledgebases, add the connector once per knowledgebase. Legacy API tokens always have full read & write access to their knowledgebase.
Legacy: connecting with a static API token
Clients that don't support OAuth (or where you prefer a fixed key) can authenticate with a Bearer token. Generate one in the Perfect Wiki settings of the knowledgebase you want to expose — each token is scoped to a single knowledgebase.
For Claude Desktop, Cursor, Windsurf and similar clients, add this to the MCP configuration file:
{
"mcpServers": {
"perfect-wiki": {
"type": "http",
"url": "https://api.perfectwiki.xyz/mcp",
"headers": {
"Authorization": "Bearer your-api-token"
}
}
}
}Restart the client after saving the configuration.
Tip: you can register multiple Perfect Wiki knowledgebases side-by-side — just give each one a unique server name and use the API token for the matching knowledgebase. A useful convention is perfect-wiki-[kb-name], for example:
claude mcp add --transport http -s user perfect-wiki-human-resources-kb https://api.perfectwiki.xyz/mcp \
--header "Authorization: Bearer hr-kb-token"
claude mcp add --transport http -s user perfect-wiki-engineering-kb https://api.perfectwiki.xyz/mcp \
--header "Authorization: Bearer eng-kb-token"
claude mcp add --transport http -s user perfect-wiki-sales-kb https://api.perfectwiki.xyz/mcp \
--header "Authorization: Bearer sales-kb-token"Claude will then expose each knowledgebase's tools under its own namespace, so you can ask it to search or update a specific knowledgebase by name.
Verifying the connection
Once configured, your client should expose Perfect Wiki tools such as:
- get_knowledgebase — get info about the connected knowledgebase
- list_pages — list all pages
- get_page — read a specific page
- create_page — create a new page
- update_page — update an existing page
- delete_page — delete a page
- ask — ask a natural-language question against your knowledgebase
Try asking your assistant: "List the pages in my Perfect Wiki knowledgebase."
FAQ
Should I use OAuth or an API token?
Use OAuth whenever your client supports it (Claude web/desktop/mobile, ChatGPT, Claude Code). It's more secure — you sign in with your own account, grant only the permissions you need, and can revoke access without touching config files. API tokens remain supported as a legacy option for clients without OAuth.
Where do I get an API token (legacy)?
Open the Perfect Wiki settings for the knowledgebase you want to expose and generate a Bearer token there. Each token is scoped to a single knowledgebase.
Can one connection access multiple knowledgebases?
No. Both OAuth connections and API tokens are scoped to a single knowledgebase. To connect several knowledgebases, add the connector once per knowledgebase (OAuth) or register one MCP server per token (legacy).
Can the assistant delete or overwrite my pages?
Only if the connection has write access. With OAuth, write access requires the wiki:write permission granted on the consent screen — connect with read-only permissions if you want a safe setup. Legacy tokens always have full access. Most MCP clients additionally ask for your confirmation before running a write tool.
How do I revoke access?
For OAuth connections, simply remove the connector in your assistant's settings — its access stops working shortly after. For legacy tokens, revoke the token in Perfect Wiki settings and generate a new one; any client configured with the old token stops working immediately.
The assistant says a tool needs a permission it doesn't have. What's wrong?
The connection was approved with fewer permissions (e.g. read-only). Remove the connector and reconnect, granting wiki:write on the consent screen.
Is my knowledgebase content sent to the LLM provider?
Yes. When you ask Claude (or another MCP client) a question, the tool results it pulls from Perfect Wiki are passed to the LLM as part of the conversation, following your LLM provider's data policy. The Perfect Wiki MCP server itself only forwards the requests your client makes.
My client doesn't show the Perfect Wiki tools. What's wrong?
Most common causes: the client wasn't restarted after editing the config, the OAuth connection wasn't completed (finish the sign-in and consent flow), the Authorization header is missing or malformed (legacy tokens must be sent as Bearer your-api-token), the token was revoked, or the transport type in the config doesn't match http. Check your client's MCP logs for the exact error.
Can I use the server with LLMs other than Claude and ChatGPT?
Yes. Any MCP-compatible client works — Cursor, Windsurf, Zed, VS Code (Copilot agent mode), custom agents built on the MCP spec, etc. The server is model-agnostic: use OAuth if the client supports it, or a legacy token header otherwise.
Is there a request quota or rate limit?
The MCP server is backed by the Perfect Wiki API, so the same quotas and rate limits as your plan's API apply. Heavy usage (e.g. bulk list_pages loops) can hit those limits — prefer the ask tool for broad questions over iterating every page.
Need help?
If something doesn't work as expected, contact support.