Add Perfect Wiki to VS Code and GitHub Copilot's agent mode can search your team's runbooks, API specs and how-to guides without leaving the editor — and turn what it figures out into documentation others can reuse.
Drop the Perfect Wiki server into .vscode/mcp.json or run MCP: Add Server from the Command Palette. VS Code registers with Perfect Wiki automatically and asks you to sign in.
In agent mode, Copilot can ask Perfect Wiki how your team does things, open the relevant runbook or spec, and — once you approve — create the page that was missing so the next person doesn't have to ask.
.vscode/mcp.json in your workspace, or run MCP: Open User Configuration to add it for every workspace.perfect-wiki entry under servers with "type": "http" and "url": "https://api.perfectwiki.xyz/mcp" — or run MCP: Add Server and choose HTTP.More details in the Perfect Wiki MCP server guide and VS Code's MCP documentation.
VS Code prompts for the token the first time the server starts and stores it securely, so it never appears in mcp.json. Use ${input:…} rather than ${env:…} for headers.
Deployment steps, feature-flag conventions, who owns which service — Copilot pulls it from Perfect Wiki while you stay in the file you’re working on.
When Copilot works something out that isn’t documented, have it write the page. Knowledge stops living only in one senior engineer’s head.
Before changing a fragile area, Copilot checks past incident postmortems so the same failure doesn’t come back.
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 →.vscode/mcp.json applies to one workspace and can be committed for the team. The user configuration, opened with MCP: Open User Configuration, makes Perfect Wiki available in every workspace on your machine.
No. VS Code uses dynamic client registration, so it registers itself with the Perfect Wiki MCP server and simply asks you to sign in.
Input variables prompt once and store the value securely. Environment-variable substitution in MCP headers has known issues in VS Code, so ${input:perfect-wiki-token} is the reliable option.
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 VS 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 →
Keep your SOPs, manuals and FAQs in Perfect Wiki — and give your whole team answers right where they work.