AI knowledge base for GitHub Copilot CLI.
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.
Connect GitHub Copilot CLI in two minutes.
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.
- →Added with one copilot mcp add command
- →OAuth sign-in or a Bearer token — both supported
- →Per-project config via .mcp.json when you need it
Your processes, followed step by step — from the terminal.
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.
- →Release and deploy checklists executed, not just read
- →On-call handbooks available while you’re in a shell
- →Process pages updated when a step no longer applies
make release-ios command on the checklist page.How to connect Perfect Wiki to GitHub Copilot CLI.
- 1Run
copilot mcp add --transport http perfect-wiki https://api.perfectwiki.xyz/mcp— or type/mcp addinside a Copilot session for the interactive flow. - 2Start
copilotand ask something that needs your wiki. Follow the sign-in prompt the first time the server is used. - 3Sign in to Perfect Wiki, choose the knowledge bases and the access level, then click Allow access.
- 4For a single repository, put the server in
.mcp.jsonor.github/mcp.jsoninstead 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 — sign in with OAuth instead to cover several knowledge bases with one connection.
What your team does with Perfect Wiki in GitHub Copilot CLI.
On-call without the scramble
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.
Release checklists that run
Copilot reads the checklist, executes the steps you approve, and keeps the page honest when a step is outdated.
Contribution rules for every repo
Branch naming, commit conventions and review rules live in one wiki page. Copilot applies them when it creates branches and PR descriptions.
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 →Frequently asked questions
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.
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, GitHub Copilot CLI 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. GitHub Copilot CLI 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 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 →
Put your SOPs to work in GitHub Copilot CLI.
Keep your SOPs, manuals and FAQs in Perfect Wiki — and give your whole team answers right where they work.