AI knowledge base for Kiro.
Connect Perfect Wiki to Kiro and your specs start from what the team already knows: product requirements, domain rules and engineering standards — with one config file shared by the Kiro IDE and Kiro CLI.
Connect Kiro in two minutes.
Add a single entry to your Kiro MCP config and Kiro opens the Perfect Wiki sign-in in your browser. The same file powers both the IDE and kiro-cli, so you only set it up once.
- →OAuth sign-in opens automatically — no token to manage
- →User-level or workspace-level config, your choice
- →One setup for the Kiro IDE and Kiro CLI
Specs built on your requirements — not on guesses.
When Kiro drafts requirements, a design or a task list, it can pull the matching product and domain pages from Perfect Wiki. Once the feature is built, it can publish the final spec back so the rest of the company sees it.
- →Requirements that reference your real product rules
- →Designs aligned with documented architecture decisions
- →Finished specs published to the wiki for non-engineers
How to connect Perfect Wiki to Kiro.
- 1Open the Command Palette and run Kiro: Open user MCP config (JSON) — or create
.kiro/settings/mcp.jsonin your workspace. - 2Add the
perfect-wikiserver with the URLhttps://api.perfectwiki.xyz/mcpand save. The file is shared by the IDE and Kiro CLI;kiro-cli mcp addhas no URL flag, so edit the JSON directly. - 3Kiro opens the Perfect Wiki sign-in in your browser — choose the knowledge bases and the access level, then click Allow access. In the CLI,
/mcp authsigns you in again. - 4Try it: “Summarize our onboarding requirements from Perfect Wiki.”
More details in the Perfect Wiki MCP server guide and Kiro's MCP documentation.
Kiro only expands ${PERFECT_WIKI_TOKEN} if the variable is approved under Settings → "Mcp Approved Env Vars". The token is scoped to one knowledge base and has read & write access.
What your team does with Perfect Wiki in Kiro.
Requirements from the source of truth
Product managers keep requirements and business rules in Perfect Wiki. Kiro reads them when it writes a spec, so nothing gets retyped or lost.
Steer agents with team standards
Point Kiro at your coding standards and security checklist in the wiki instead of copying them into every repository.
Share specs beyond engineering
Publish the finished design to the wiki so support, sales and success know exactly what shipped.
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 ~/.kiro/settings/mcp.json for all workspaces, or .kiro/settings/mcp.json for one workspace. Both the Kiro IDE and Kiro CLI read the same files.
Yes. The Amazon Q Developer CLI now forwards to Kiro CLI, and its MCP configuration migrates from ~/.aws/amazonq/mcp.json to ~/.kiro/settings/mcp.json. Add Perfect Wiki there and it works in Kiro.
In Kiro CLI, run /mcp auth to restart the Perfect Wiki sign-in. In the IDE, the browser sign-in opens when Kiro connects to a server that needs authentication.
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, Kiro 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. Kiro 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 Kiro 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 Kiro.
Keep your SOPs, manuals and FAQs in Perfect Wiki — and give your whole team answers right where they work.