AI knowledge base for Zed.
Zed is fast; hunting through a browser tab for docs isn’t. Add Perfect Wiki as a context server, and the Agent Panel answers from your team’s docs, API references and incident notes without you leaving the editor.
Connect Zed in two minutes.
Add a context_servers entry with the Perfect Wiki URL. When there’s no Authorization header, Zed asks you to sign in with OAuth on its own.
- →A few lines in settings.json — or Add Remote Server in the UI
- →OAuth prompt appears automatically, no token required
- →Perfect Wiki tools available to the Agent Panel
Your team’s memory, one panel away.
Past incidents, API conventions and internal how-tos become context the agent can fetch while it works — and pages it can write when a fix deserves documenting.
- →Incident history and postmortems searchable from the editor
- →Internal API references fetched as full pages
- →New learnings saved back as wiki pages
SEARCH_RATE_LIMIT to 200 — your .env.staging still has 50.How to connect Perfect Wiki to Zed.
- 1Open Settings → AI → MCP Servers → Add Server → Add Remote Server — or edit
~/.config/zed/settings.jsondirectly. - 2Add
perfect-wikiundercontext_serverswith"url": "https://api.perfectwiki.xyz/mcp". - 3Leave out the Authorization header — Zed prompts you to sign in. Log in to Perfect Wiki, choose the knowledge bases and the access level, then click Allow access.
- 4Open the Agent Panel and ask, for example “How do we version internal APIs?”
More details in the Perfect Wiki MCP server guide and Zed'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 Zed.
Postmortems at your fingertips
Before you debug from scratch, the agent checks whether the team has seen this failure before and what fixed it.
Internal APIs, in context
Internal services rarely have public docs. The agent reads your wiki’s API pages so generated clients use the right endpoints and auth.
Document the fix while it’s fresh
Once the bug is solved, turn the debugging session into a troubleshooting page the next person will actually find.
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
In Settings → AI → MCP Servers → Add Server → Add Remote Server, or directly in ~/.config/zed/settings.json under context_servers. Older guides mention an “Add Custom Server” button — the current label is Add Remote Server.
If the server entry has no Authorization header, Zed starts the OAuth flow automatically: sign in to Perfect Wiki, choose the knowledge bases and the access level, and allow access. Add a header only if you want to use an API token instead.
Zed refers to MCP servers as context servers, which is why the settings key is context_servers. It is the same Model Context Protocol, so the standard Perfect Wiki server works as-is.
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, Zed 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. Zed 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 Zed 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 Zed.
Keep your SOPs, manuals and FAQs in Perfect Wiki — and give your whole team answers right where they work.