Employees ask AI. Your SOPs answer.
Your team already asks ChatGPT, Claude and Copilot how things work. Connect the Perfect Wiki MCP server, and those assistants answer from your SOPs, policies and FAQs — the current version, with a link to the source page — instead of guessing.
Why teams put Perfect Wiki behind their AI assistant.
Pointing an assistant at a folder of files gets you search. Answering employee questions well takes approved content, sources and access control.
Answers, not page dumps
The ask tool returns a ready answer drawn from your SOPs and FAQs, plus the pages it came from — the assistant doesn’t have to read the whole wiki to reply.
A source with every answer
Each answer links to the exact Perfect Wiki page, so employees can open the full procedure before they act on it.
Always the current version
Assistants read the live wiki, not an uploaded copy. Update a policy once, and every assistant answers with the new version from the next question.
One sign-in, every knowledge base
HR, IT, Sales, Support — connect all of them or just a few. The assistant searches across every knowledge base in the connection.
Each person, their own access
Employees sign in with their own Perfect Wiki account, so the assistant only reaches the knowledge bases they can open — and you can keep it read-only.
See what people ask
Questions assistants send to Perfect Wiki show up in your reports, including the ones your wiki couldn’t answer — so you know which SOP or FAQ to write next.
Ask in any assistant. Get the answer from your SOP.
An employee asks ChatGPT, Claude or Copilot how something works at your company. The assistant calls Perfect Wiki, gets an answer built from your SOPs, policies and FAQs, and replies with a link to the source page.
- →AI answers from your SOPs, policies and FAQs
- →A link to the source page with every answer
- →Searches all connected knowledge bases at once
Source: 📄 PTO & Vacation Policy
Sign in once — no tokens, no client IDs.
Add the server URL and sign in with your Perfect Wiki account. The server supports OAuth dynamic client registration, so assistants register themselves. On one consent screen you choose the access level and the knowledge bases — and you can revoke access any time.
- →Endpoint: api.perfectwiki.xyz/mcp — Streamable HTTP
- →Read only or Read & write — chosen at sign-in
- →All knowledge bases you can access, or only the ones you select
- Signed in as
- anna@acme.com
- Access level
- Read only
- Knowledge bases
- All you can access · 4
- Added later
- Included automatically
Coding agents & IDEs: one config snippet.
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.
- →Copy-paste snippets for every popular client — see the guides below
- →Clients without OAuth use a Bearer token scoped to one knowledge base
- →Claude Code, Codex and Gemini CLI: one command, then sign in
Not just answers — SOP owners keep the wiki current.
Give SOP and policy owners read & write access, and they create and update pages by talking to the assistant. Clients ask for confirmation before anything is written, and edits are saved under the person's own account.
- →Draft new SOPs and FAQ pages straight from the conversation
- →Update a policy once — every assistant answers with the new version
- →Writes only where the person can edit in Perfect Wiki
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 CleaningCleaning Chemical Dilution SOP Template
- Commercial CleaningDeep Cleaning SOP Template
- Commercial CleaningFloor Cleaning and Mopping SOP Template
- Commercial CleaningJanitorial Closet and Equipment Care SOP Template
- Commercial CleaningMove-Out Cleaning SOP Template
- Commercial CleaningOffice Cleaning SOP Template
Frequently asked questions
It is the official Model Context Protocol (MCP) server for Perfect Wiki. It lets any MCP-compatible AI assistant or agent answer questions from your SOPs, policies and FAQs with sources, and create or update pages — so your wiki becomes the knowledge source behind the AI tools your team already uses.
Yes — it’s built for that. Keep your SOPs, policies and FAQs in Perfect Wiki and connect the MCP server to the assistant your company uses. Employees get answers from those pages with a link to the source, and questions the wiki couldn’t answer show up in your Perfect Wiki reports. Give employees read-only access and let SOP owners connect with read & write.
Any MCP client that supports remote (Streamable HTTP) servers: Claude, ChatGPT, Microsoft Copilot (as a built-in agent or a Copilot Studio tool), Claude Code, OpenAI Codex, Cursor, VS Code with GitHub Copilot, Windsurf, Gemini CLI, Zed, Cline, JetBrains AI Assistant, n8n and more. Each client has a setup guide on this page.
No. The Perfect Wiki MCP server supports OAuth 2.1 with dynamic client registration, so Claude, ChatGPT, Copilot Studio, VS Code, Cursor and other clients register themselves. Paste the server URL and sign in — leave any Client ID and Client Secret fields empty.
Use OAuth whenever your client supports it — each person signs in with their own account, picks the knowledge bases and the access level, and can revoke access without touching config files. Static API tokens remain supported for scripts and clients without OAuth; each token covers one knowledge base with read & write access.
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, your AI assistant 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. your AI assistant 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 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 →
Put your SOPs to work in every AI tool.
Keep your SOPs, manuals and FAQs in Perfect Wiki — and give your whole team answers right where they work.