Bring your teamβs wiki into IntelliJ IDEA, PyCharm, WebStorm and every other JetBrains IDE. Connect the Perfect Wiki MCP server to AI Assistant or Junie, and your coding agent works from the same specs and standards your team does.
Junie reads MCP servers from mcp.json and supports OAuth sign-in. For AI Assistant, paste the server as JSON in its MCP settings together with an API token header.
Product specs, domain rules and coding standards stop living in a separate tab. The agent fetches the page it needs, implements against it, and can note what changed.
PricingService.kt with a test for each rule, including the no-stacking case.~/.junie/mcp/mcp.json (all projects) or .junie/mcp/mcp.json (one project).perfect-wiki with "url": "https://api.perfectwiki.xyz/mcp". To authorize from the Junie CLI, run /mcp, select perfect-wiki and choose Authorize, then sign in to Perfect Wiki and allow access.More details in the Perfect Wiki MCP server guide and JetBrains AI'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.
Invoicing, pricing and eligibility logic is implemented from the rules page product maintains β and checked against it later.
Pair the code with the architecture overview and module ownership docs so the agent can explain why things are built the way they are.
Ask the agent to review changes against your language style guides and conventions before a human reviewer spends time on them.
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.
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 βYes, both connect to remote MCP servers. Add it in Settings | Tools | AI Assistant | Model Context Protocol (MCP), or in Settings | Tools | Junie | MCP Settings β Junie also reads ~/.junie/mcp/mcp.json.
Junie documents OAuth sign-in for remote servers, so you can connect without a token. AI Assistant doesnβt document OAuth for MCP servers, so the reliable option there is a Perfect Wiki API token in the Authorization header.
Any JetBrains IDE where AI Assistant or Junie is available β including IntelliJ IDEA, PyCharm, WebStorm, GoLand, PhpStorm and Rider. The MCP configuration is the same everywhere.
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 JetBrains AI 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 β
Keep your SOPs, manuals and FAQs in Perfect Wiki β and give your whole team answers right where they work.