AI knowledge base for Visual Studio.
Bring Perfect Wiki into Visual Studio's Copilot agent mode. Your .NET team gets answers from internal specs, coding guidelines and deployment runbooks right next to the solution — and the agent can document what it builds.
Connect Visual Studio in two minutes.
Add a small .mcp.json file to your user profile or solution, then click the Authentication Required CodeLens that appears above the server to sign in with Perfect Wiki.
- →Visual Studio 2022 (17.14+) and Visual Studio 2026
- →Per-user or per-solution configuration
- →Sign in right from the CodeLens in the config file
Copilot builds to your specs — and documents the result.
In agent mode, Copilot can read the design doc for the feature you're building, check your .NET coding guidelines, and write up the new endpoint or configuration in Perfect Wiki once it's done.
- →Design docs and guidelines read inside the IDE
- →Consistent patterns across projects in a solution
- →New endpoints and settings documented as they land
POST /invoices/{id}/approve with the role check and audit entry the design requires. The endpoint is documented in “Invoices API — approvals” in your Engineering wiki.How to connect Perfect Wiki to Visual Studio.
- 1Create
%USERPROFILE%\.mcp.jsonto use Perfect Wiki in every solution, or<solution>\.mcp.jsonfor one solution. - 2Add a
perfect-wikientry underserverswith"url": "https://api.perfectwiki.xyz/mcp". Alternatively, open Copilot Chat → Agent mode → Tools → + to add a custom MCP server. - 3Click the Authentication Required CodeLens above the server and choose Authenticate. Sign in to Perfect Wiki and click Allow access.
- 4In Copilot Chat, switch to Agent mode and make sure the perfect-wiki tools are enabled.
More details in the Perfect Wiki MCP server guide and Visual Studio's MCP documentation.
Visual Studio also reads .vs\mcp.json and .vscode\mcp.json in the solution folder, so a config shared with VS Code users works too. Sign-in uses OAuth — nothing secret goes in the file.
What your team does with Perfect Wiki in Visual Studio.
Specs next to the solution
Business rules and design docs written by product and architects are one question away while Copilot implements the feature in C#.
Consistent .NET conventions
Keep your guidance on logging, dependency injection and EF Core usage in the wiki, and let Copilot follow it across every project.
Deployment runbooks in the IDE
Before publishing, Copilot pulls the environment runbook — config transforms, slots, approvals — so releases follow the documented path.
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
Visual Studio 2022 version 17.14 or later and Visual Studio 2026, using GitHub Copilot in agent mode.
Use %USERPROFILE%\.mcp.json for all solutions, or <solution>\.mcp.json, <solution>\.vs\mcp.json or .vscode\mcp.json for a single solution. The format uses a top-level servers object.
Once the server is in your .mcp.json, an Authentication Required CodeLens appears above it. Click it, choose Authenticate and complete the Perfect Wiki sign-in in your browser.
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, Visual Studio 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. Visual Studio 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 Visual Studio 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 Visual Studio.
Keep your SOPs, manuals and FAQs in Perfect Wiki — and give your whole team answers right where they work.