AI knowledge base for Cursor.
Install the Perfect Wiki MCP server in Cursor and the agent can look up your coding standards, API docs and onboarding guides while it edits — then keep those pages accurate as the codebase evolves.
Connect Cursor in two minutes.
Click Add to Cursor or paste a three-line entry into mcp.json. Cursor notices the server needs sign-in and walks you through connecting your Perfect Wiki account.
- →One-click install link — no JSON editing required
- →Global or per-project configuration
- →OAuth sign-in, so no secrets live in mcp.json
The agent knows your conventions — before it edits a file.
Cursor's agent can query Perfect Wiki mid-task: it finds the style guide for the component it's touching, reads the API contract, and proposes an update to the docs when behavior changes.
- →Refactors that follow your documented patterns
- →API contracts pulled in while wiring up an integration
- →Doc updates proposed alongside the code diff
Dialog wrapper, validate on blur and keep the primary action on the right. I've applied all three and removed the custom focus trap.How to connect Perfect Wiki to Cursor.
- 1Use the Add to Cursor button above, or open
~/.cursor/mcp.json(all projects) or.cursor/mcp.json(this project only). - 2If editing by hand, add a
perfect-wikientry undermcpServerswith"url": "https://api.perfectwiki.xyz/mcp". - 3Open Customize → MCPs in the Cursor sidebar and follow the sign-in prompt for perfect-wiki.
- 4Sign in to Perfect Wiki, pick the knowledge base and click Allow access. The tools are now available to the agent.
More details in the Perfect Wiki MCP server guide and Cursor's MCP documentation.
Cursor substitutes ${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 expose.
What your team does with Perfect Wiki in Cursor.
Onboard into an unfamiliar repo
New engineers ask Cursor how a service fits together and get answers from your architecture overviews and onboarding guides, not guesses from file names.
Wire up internal APIs correctly
Cursor reads the internal API reference from the wiki — auth headers, rate limits, error codes — while it writes the client code.
Enforce the style guide
Instead of pasting rules into prompts, keep one frontend or backend guide in Perfect Wiki and let the agent apply it to every change.
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.
Start from a ready-made SOP. Keep it alive here.
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 →Frequently asked questions
In ~/.cursor/mcp.json for all projects, or in .cursor/mcp.json inside a repository for that project only. Both use the same mcpServers format.
Yes. Commit .cursor/mcp.json with just the server URL. Because sign-in uses OAuth, the file contains no secrets — each developer connects their own Perfect Wiki account.
Add a headers object with "Authorization": "Bearer ${env:PERFECT_WIKI_TOKEN}" to the perfect-wiki entry and set that environment variable. Cursor expands ${env:NAME} in both the url and headers fields.
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 Cursor 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 Cursor.
Keep your SOPs, manuals and FAQs in Perfect Wiki — and give your whole team answers right where they work.