AI knowledge base for VS Code.
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.
Connect VS Code in two minutes.
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.
- →Works with GitHub Copilot agent mode
- →Workspace config or user-wide config — your choice
- →Automatic OAuth client registration, no app setup
Copilot answers from your docs — and fills the gaps.
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.
- →Team know-how available in Copilot Chat
- →Specs and runbooks read directly from the source
- →Missing docs created from the conversation
How to connect Perfect Wiki to VS Code.
- 1Create
.vscode/mcp.jsonin your workspace, or run MCP: Open User Configuration to add it for every workspace. - 2Add a
perfect-wikientry underserverswith"type": "http"and"url": "https://api.perfectwiki.xyz/mcp"— or run MCP: Add Server and choose HTTP. - 3When VS Code starts the server, accept the sign-in prompt, log in to Perfect Wiki, choose the knowledge bases and the access level, then click Allow access.
- 4Open Copilot Chat, switch to Agent mode and ask about your docs.
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.
What your team does with Perfect Wiki in VS Code.
Answers without switching tabs
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.
Capture tribal knowledge
When Copilot works something out that isn’t documented, have it write the page. Knowledge stops living only in one senior engineer’s head.
Postmortems linked to code
Before changing a fragile area, Copilot checks past incident postmortems so the same failure doesn’t come back.
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
.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.
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, VS Code 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. VS Code 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 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 →
Put your SOPs to work in VS Code.
Keep your SOPs, manuals and FAQs in Perfect Wiki — and give your whole team answers right where they work.