Your SOPs, manuals and FAQs live in Perfect Wiki. The MCP server turns them into an AI-powered knowledge base for Claude, ChatGPT, Cursor, Codex and any other MCP client β answers with sources, and page updates straight from chat.
Add the server URL to your client and sign in with your Perfect Wiki account. On the consent screen you pick the knowledge base and grant read-only or read & write access β and you can revoke it any time.
Cursor, Windsurf, Zed, Gemini CLI and most other clients read a small MCP config file. Paste the server URL, sign in (or add a legacy API token header), and your knowledge base shows up as a set of tools.
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.
Ask a natural-language question and get an AI answer with sources.
List every page in the connected knowledge base.
Read the full content of a specific page.
Create a new page β draft SOPs straight from chat.
Update an existing page, so SOPs never go stale.
Remove pages that are no longer needed.
Get info about the connected knowledge base.
Download any of our 284 standard operating procedure templates in Word, PDF, Excel or CSV, no sign-up needed. Then put it in Perfect Wiki so your team can find it and ask about it.
Browse all 284 SOP templates βIt is the official Model Context Protocol (MCP) server for Perfect Wiki. It lets any MCP-compatible AI assistant or coding agent search your knowledge base, answer questions with sources, and create or update pages β turning your wiki into an AI-powered knowledge base inside the tools your team already uses.
Any MCP client that supports remote (Streamable HTTP) servers: Claude, ChatGPT, Microsoft Copilot Studio, Claude Code, OpenAI Codex, Cursor, VS Code with GitHub Copilot, Windsurf, Gemini CLI, Zed, Cline, JetBrains AI Assistant and more. Each client has a setup guide on this page.
Use OAuth whenever your client supports it β you sign in with your own account, grant only the permissions you need, and can revoke access without touching config files. Static API tokens remain supported for scripts and clients without OAuth.
Only if you allow it. When you connect with OAuth you choose read-only (wiki:read) or read & write (wiki:write) on the consent screen. Legacy API tokens always have full access to their knowledge base. Most MCP clients also ask for your confirmation before running a tool that writes.
Yes. Each connection is scoped to one knowledge base, so add the server once per knowledge base and give each a unique name β for example perfect-wiki-hr and perfect-wiki-engineering. The assistant can then search or update a specific knowledge base by name.
The Perfect Wiki MCP server only forwards the requests your AI assistant makes. Tool results β the pages and answers it fetches β are passed to the model as part of the conversation and handled under your AI provider's data policy.
The MCP server is included in every Perfect Wiki plan, and the same API rate limits apply. You can try it with the 14-day free trial β no credit card required.
Didn't find what you're looking for? Contact our support β
Keep your SOPs, manuals and FAQs in Perfect Wiki β and give your whole team answers right where they work.