Official Perfect Wiki MCP Server10,000+ companies

One MCP server. Every AI tool your team uses.

Your SOPs, manuals and FAQs live in Perfect Wiki. The MCP server connects them to Claude, Cursor, VS Code, Codex and any other MCP client — AI answers with sources, and page updates straight from chat.

▸https://api.perfectwiki.xyz/mcp

Start 14-day free trial→orBook a call with us

No credit cardSetup in under 10 minutesCancel anytime

Works with every MCP client

Claude →Claude Desktop & Claude Code

Cursormcp.json

VS CodeGitHub Copilot agent mode

OpenAI Codexconfig.toml

Windsurfmcp.json

Gemini CLIsettings.json

ClineVS Code extension

JetBrains AIAI Assistant

01CLI setup

One command and you're connected.

Grab an API token from your Perfect Wiki settings and register the server — in Claude Code it's a single terminal command. Tokens are scoped per knowledge base, so you stay in control of what each client can see.

→Endpoint: api.perfectwiki.xyz/mcp — HTTP transport
→One Bearer token per knowledge base
→Connect several knowledge bases as separate servers

Terminal

$ claude mcp add --transport http \ -s user perfect-wiki \ https://api.perfectwiki.xyz/mcp \ --header "Authorization: Bearer <your-token>"

✓ Added HTTP MCP server "perfect-wiki"

$ claude "What's our refund policy?"

⚙ ask → searching your knowledge base…

02Config-file setup

Everywhere else: one JSON snippet.

Cursor, Windsurf, VS Code, Claude Desktop and most other clients read the same MCP configuration format. Paste the snippet, restart the client, and your knowledge base shows up as a set of tools.

→Same snippet works across mcp.json-based clients
→OpenAI Codex uses the equivalent config.toml entry
→Restart the client and the tools appear automatically

mcp.json · Cursor / Windsurf / VS Code

{ "mcpServers": { "perfect-wiki": { "type": "http", "url": "https://api.perfectwiki.xyz/mcp", "headers": { "Authorization": "Bearer your-api-token" } } } }

03Read & write

Not just search — your AI maintains the wiki.

MCP clients get the full toolset: ask questions, read pages, create new ones, and update existing SOPs. Your client asks for confirmation before anything is written, so nothing changes without you.

→AI answers grounded in your internal docs, with sources
→Draft and update SOPs straight from the conversation
→Clients confirm before create, update, or delete runs

Claude

Update our refund SOP — returns are now accepted for 30 days instead of 14.

⚙ get_page · Refund Policy SOP⚙ update_page ✓

Done — I've updated "Refund Policy SOP" to the 30-day window and adjusted the two examples that mentioned 14 days. The page is live in your knowledge base.

The full toolset

ask()

Ask a natural-language question and get an AI answer with sources.

list_pages()

List every page in the connected knowledge base.

get_page()

Read the full content of a specific page.

create_page()

Create a new page — draft SOPs straight from chat.

update_page()

Update an existing page, so SOPs never go stale.

delete_page()