AI knowledge base for Claude Code.
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.
Connect Claude Code in two minutes.
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.
- →OAuth sign-in from the terminal — no tokens to paste
- →User scope: configure once, use it in every repo
- →Share the setup via .mcp.json — nothing secret gets committed
Claude Code reads your runbooks — and updates the docs.
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.
- →Grounds code changes in your engineering standards
- →Pulls runbooks and architecture docs into context on demand
- →Keeps wiki pages in sync with what actually shipped
webhooks/handler.ts and added the new retry behaviour to the Payments service page.How to connect Perfect Wiki to Claude Code.
- 1Add the server from your terminal:
claude mcp add --transport http --scope user perfect-wiki https://api.perfectwiki.xyz/mcp - 2Start Claude Code, run
/mcp, select perfect-wiki and choose Authenticate. You can also runclaude mcp login perfect-wiki. - 3In the browser, sign in to Perfect Wiki, choose the knowledge bases and the access level, then click Allow access.
- 4Ask away — for example “Search Perfect Wiki for our deployment checklist.”
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 — sign in with OAuth instead to cover several knowledge bases with one connection.
What your team does with Perfect Wiki in Claude Code.
Code that follows your conventions
Claude Code checks your API guidelines, coding standards and architecture decisions before it writes a line — so reviews stop catching the same mistakes.
Runbooks during incidents
Pull the right runbook into the terminal while you debug, and let Claude Code walk through the steps with you.
Docs that ship with the code
After a change lands, have Claude Code update the service page, the changelog or the onboarding guide — no separate docs ticket.
Ask a question in plain language and get an AI answer from your SOPs and FAQs, with the source pages.
See which knowledge bases the connection covers and the access level for each.
List every page in a 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 the name and access level of one knowledge base.
Start from a ready-made SOP. Keep it alive here.
Download any of our 294 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 294 SOP templates →- Commercial KitchenFood Receiving and Storage SOP Template
- Commercial KitchenKitchen Allergen Control SOP Template
- Commercial KitchenKitchen Cleaning SOP Template
- Commercial KitchenKitchen Food Preparation SOP Template
- Commercial KitchenKitchen Handwashing SOP Template
- Commercial KitchenKitchen Knife Safety SOP Template
Frequently asked questions
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.
Uploaded files are a snapshot: they go stale the moment a policy changes, and they stay in one chat or project. Through the MCP server, Claude Code reads the current version of your SOPs and FAQs from Perfect Wiki every time, links to the source page, and only reaches the knowledge bases you connect.
Only if you allow it. When you sign in with OAuth you choose Read only or Read & write on the consent screen, and writes only work in knowledge bases where you can edit. Legacy API tokens always have full access to their one knowledge base. Most MCP clients also ask for your confirmation before running a tool that writes.
Yes, with a single connection. When you sign in, choose all knowledge bases you can access (including ones you get access to later) or only the ones you select. Claude Code can search across all of them at once and has to name the target knowledge base for every change. API tokens cover one knowledge base each, so add one server entry per token.
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 →
Put your SOPs to work in Claude Code.
Keep your SOPs, manuals and FAQs in Perfect Wiki — and give your whole team answers right where they work.