AI knowledge base for Windsurf.
Windsurf is now Devin Desktop — and Perfect Wiki works with both of its agents. Connect the MCP server, and Devin or Cascade can pull your security policies, specs and support playbooks into every task, then keep those pages accurate.
Connect Windsurf in two minutes.
For the Devin Local agent, two commands add the server and sign you in. Cascade reads its own mcp_config.json — that setup is in the guide below.
- →devin mcp add registers Perfect Wiki for your user
- →devin mcp login takes care of the Perfect Wiki sign-in
- →Cascade supported through mcp_config.json with serverUrl
Security rules and specs, checked before the code is.
Your agent consults Perfect Wiki the way a senior engineer would: it reads the policy or spec that applies, follows it, and can update the page when the implementation changes the rules.
- →Security and compliance policies applied during the task
- →Specs and runbooks pulled in without leaving the editor
- →Page updates only with the write access you grant
admin/export.ts — and I removed a field that would have logged an email address.How to connect Perfect Wiki to Windsurf.
- 1For the Devin Local agent, run
devin mcp add -s user perfect-wiki https://api.perfectwiki.xyz/mcp - 2Run
devin mcp login perfect-wiki, sign in to Perfect Wiki in the browser, choose the knowledge bases and the access level, then click Allow access. - 3Using Cascade? Click the MCPs icon in the Cascade panel (or Devin Settings → Cascade → MCP Servers) and add
perfect-wikito~/.codeium/windsurf/mcp_config.jsonwith aserverUrl— see the token example. - 4Ask your agent something like “What does our incident policy say about customer notifications?”
More details in the Perfect Wiki MCP server guide and Windsurf's MCP documentation.
Cascade expands ${env:PERFECT_WIKI_TOKEN} from your environment, so the token itself stays out of the file. Generate it in the Perfect Wiki settings of the knowledge base you want to connect.
What your team does with Perfect Wiki in Windsurf.
Security policies applied by default
Data handling, logging and access rules get checked while the code is written, instead of surfacing in a security review two weeks later.
Escalations with the full story
When support escalates a bug, the agent pulls the known-issues page and past workarounds before proposing a fix.
New engineers ramp faster
Point new hires’ agents at your onboarding docs and let them set up the environment and learn the codebase step by step.
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
Yes. Windsurf was renamed Devin Desktop in June 2026, and its documentation moved to docs.devin.ai. The Perfect Wiki MCP server works the same way — with the Devin Local agent and with Cascade.
Cascade reads ~/.codeium/windsurf/mcp_config.json, with the server URL under serverUrl. The Devin Local agent keeps its own config in ~/.config/devin/mcp_config.json and can import existing Windsurf and Cursor MCP configs.
Reference an environment variable: set the Authorization header to Bearer ${env:PERFECT_WIKI_TOKEN} and export PERFECT_WIKI_TOKEN in your shell. With the Devin Local agent you can skip tokens entirely and sign in with devin mcp login.
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, Windsurf 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. Windsurf 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 Windsurf 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 Windsurf.
Keep your SOPs, manuals and FAQs in Perfect Wiki — and give your whole team answers right where they work.