Your SOPs and FAQs, built into Copilot.
The Perfect Wiki agent comes with the Perfect Wiki app for Microsoft Teams. Employees open it in Microsoft 365 Copilot, ask how things work, and get the answer from your SOPs, policies and FAQs — with a link to the exact page. No Copilot Studio, no connectors to configure.
Works out of the box — no Copilot Studio needed.
The Perfect Wiki agent ships inside the Perfect Wiki app. If your team already uses Perfect Wiki in Teams, the agent is ready in Copilot: add it from the agent list, sign in once with your Perfect Wiki account, and start asking.
- →Comes with the Perfect Wiki app for Microsoft Teams
- →One sign-in — no Graph connector, OpenAPI spec or API token
- →Choose all your knowledge bases or only selected ones
Employees ask Copilot — your SOPs answer.
The agent searches every knowledge base you connected and answers from the matching SOP, policy or FAQ page, with a link so people can check the full procedure. When the wiki doesn't cover a question, it says so instead of making up a policy.
- →Answers grounded in your wiki, with links to the source pages
- →One question searches HR, IT, Ops and every other connected knowledge base
- →Questions the wiki couldn’t answer show up in your Perfect Wiki reports
Source: 📄 Hardware Requests SOP
Policy owners update the wiki from the same chat.
With read & write access, the agent can create, update and remove pages. Copilot shows a confirmation card before anything is saved, and the change is made under the person's own Perfect Wiki account — only where they can edit.
- →Draft new SOP and FAQ pages from a conversation
- →Confirmation card before every create, update or delete
- →Edits follow each person’s Perfect Wiki permissions
Source: 📄 Travel Policy
Building your own agent? Add the MCP tool.
For a custom Copilot Studio agent — your own instructions, other tools alongside Perfect Wiki — add the Perfect Wiki MCP server as a tool. Choose OAuth 2.0 with dynamic discovery: Copilot Studio registers itself, so there's no client ID or secret to set up.
- →No custom connector or OpenAPI spec to maintain
- →Sign in with your Perfect Wiki account — the same consent screen
- →Publish the agent to Teams and Microsoft 365 Copilot
- Server name
- perfect-wiki
- Server URL
- https://api.perfectwiki.xyz/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
How to connect Perfect Wiki to Microsoft Copilot.
- 1Install Perfect Wiki in Microsoft Teams — or skip this step if your team already uses it. The Perfect Wiki agent comes with the app.
- 2In Microsoft 365 Copilot, find Perfect Wiki under Agents. If it isn't listed, click Get agents, search for Perfect Wiki and click Add.
- 3Ask your first question. When Copilot asks you to sign in, connect your Perfect Wiki account, choose the knowledge bases and the access level, then click Allow access.
- 4Ask away — for example “What’s our parental leave policy?” Every answer links to the page it came from.
More details in the Perfect Wiki MCP server guide.
Add Perfect Wiki as an MCP tool
- Open your agent (generative orchestration on) and go to Tools → Add a tool → New tool → Model Context Protocol
- Name it
perfect-wikiand enterhttps://api.perfectwiki.xyz/mcp - Pick OAuth 2.0 → Dynamic discovery and click Create
- Create a connection, sign in to Perfect Wiki, then Add to agent
Details in Microsoft's Copilot Studio MCP guide.
What your team does with Perfect Wiki in Microsoft Copilot.
HR & IT helpdesk in Copilot
Employees ask about leave, benefits, VPN or laptops in Copilot and get the answer from your HR and IT pages — fewer repeat tickets for your team.
SOPs for frontline teams
Support, sales and operations staff get the approved procedure step by step, with the SOP linked to double-check.
Policies that stay current
Policy owners update the wiki by talking to the agent. The next person who asks gets the new answer immediately.
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 →- Logistics & TransportFreight Dispatch SOP Template
- Logistics & TransportLast-Mile Delivery SOP Template
- Logistics & TransportPre-Trip Vehicle Inspection SOP Template
- Logistics & TransportProof of Delivery SOP Template
- MaintenanceBuilding Inspection SOP Template
- MaintenanceEquipment Breakdown Response SOP Template
Frequently asked questions
No. The Perfect Wiki agent is part of the Perfect Wiki app for Microsoft Teams. Add it in Microsoft 365 Copilot, sign in with your Perfect Wiki account the first time you use it, and start asking — no Copilot Studio, Graph connector or API token required.
People with a Microsoft 365 Copilot license can use the agent at no extra cost from Microsoft. Users who only have Microsoft 365 Copilot Chat may need your admin to turn on pay-as-you-go billing for agents, which Microsoft meters in Copilot Credits. On the Perfect Wiki side, any plan works.
Only the ones you pick when you sign in — all knowledge bases you can access (including ones you get access to later) or a selection. The agent never reaches a knowledge base you can’t open in Perfect Wiki, and it can only change pages where you’re an editor and granted read & write access.
Deploy the Perfect Wiki app to your users from the Microsoft 365 admin center or the Teams admin center — the agent comes with it. Each employee signs in with their own Perfect Wiki account, so they only get answers from the knowledge bases they already have access to.
The Perfect Wiki agent is ready-made: add it and ask. It answers with sources and can create or update pages. The MCP tool is for building your own Copilot Studio agent around Perfect Wiki, with your own instructions and other tools alongside it.
Yes. Copilot Studio also supports API-key authentication, so you can connect with a Perfect Wiki API token sent in the Authorization header. OAuth is recommended so each person signs in with their own Perfect Wiki account.
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, Microsoft Copilot 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. Microsoft Copilot 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 Microsoft Copilot 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 Microsoft Copilot.
Keep your SOPs, manuals and FAQs in Perfect Wiki — and give your whole team answers right where they work.