Connect Perfect Wiki to Claude Code with one command. Your coding agent reads the engineering standards, runbooks and architecture docs your team already keeps in the wiki β and updates them when the code changes.
Register the Perfect Wiki MCP server with claude mcp add, then run /mcp to sign in with your Perfect Wiki account. No API keys in your shell history, and the server is available in every project.
Claude Code asks your knowledge base before it writes code, pulls the exact page it needs into context, and updates the documentation after a change β asking for permission before anything is written.
webhooks/handler.ts and added the new retry behaviour to the Payments service page.claude mcp add --transport http --scope user perfect-wiki https://api.perfectwiki.xyz/mcp/mcp, select perfect-wiki and choose Authenticate. You can also run claude mcp login perfect-wiki.More details in the Perfect Wiki MCP server guide and Claude Code's MCP documentation.
Generate a token in the Perfect Wiki settings of the knowledge base you want to expose. Each token is scoped to a single knowledge base and has read & write access.
Claude Code checks your API guidelines, coding standards and architecture decisions before it writes a line β so reviews stop catching the same mistakes.
Pull the right runbook into the terminal while you debug, and let Claude Code walk through the steps with you.
After a change lands, have Claude Code update the service page, the changelog or the onboarding guide β no separate docs ticket.
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 βAdd the server with claude mcp add, start Claude Code and run /mcp. Select perfect-wiki, choose Authenticate and finish the sign-in in your browser. Running claude mcp login perfect-wiki does the same from your shell.
local (the default) makes the server available in the current project only. user makes it available in every project on your machine. project writes it to .mcp.json so your whole team gets it β with OAuth there is no secret in that file, each developer signs in with their own Perfect Wiki account.
Yes. Use an API token header instead of OAuth, and allow the tools you need β for example with --allowedTools mcp__perfect-wiki__ask β when running claude -p in scripts or pipelines.
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 Claude Code 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.