Register Perfect Wiki with GitHub Copilot CLI and your terminal agent can follow the release checklist, the on-call handbook and the contribution guide your team already maintains — and update them as processes change.
A single copilot mcp add command registers the server in ~/.copilot/mcp-config.json. The first time Copilot uses it, follow the sign-in prompt to connect your Perfect Wiki account.
Copilot CLI can fetch a checklist from Perfect Wiki and work through it with you: run the commands, confirm each step, and note anything that changed back on the page for the next release.
make release-ios command on the checklist page.copilot mcp add --transport http perfect-wiki https://api.perfectwiki.xyz/mcp — or type /mcp add inside a Copilot session for the interactive flow.copilot and ask something that needs your wiki. Follow the sign-in prompt the first time the server is used..mcp.json or .github/mcp.json instead of the user-wide config.More details in the Perfect Wiki MCP server guide and GitHub Copilot CLI'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.
Paged at 3am? Copilot CLI pulls the service’s on-call guide and dashboards list so you can start triage from the terminal you already have open.
Copilot reads the checklist, executes the steps you approve, and keeps the page honest when a step is outdated.
Branch naming, commit conventions and review rules live in one wiki page. Copilot applies them when it creates branches and PR descriptions.
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 →copilot mcp add writes to ~/.copilot/mcp-config.json, so the server is available in every session. For project-specific setups, Copilot CLI also reads .mcp.json or .github/mcp.json in the repository.
Use OAuth for day-to-day work — you sign in with your own Perfect Wiki account. Use an Authorization header with an API token for scripts and automation where a browser sign-in isn’t possible.
Yes. Type /mcp add in the Copilot CLI and follow the prompts to enter the server name, HTTP transport and the Perfect Wiki URL.
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 GitHub Copilot CLI 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.