AI knowledge base for OpenAI Codex.
Hook Perfect Wiki into OpenAI Codex once and every surface gets it — the CLI, the IDE extension and the Codex app. Codex looks up your specs, decisions and runbooks before it touches the code, and writes back what it learned.
Connect OpenAI Codex in two minutes.
Run codex mcp add with the Perfect Wiki URL. Codex detects that the server uses OAuth and opens your browser to sign in — the entry lands in ~/.codex/config.toml, which the CLI, IDE extension and app all share.
- →One command, browser sign-in handled automatically
- →A single config.toml for the CLI, IDE extension and desktop app
- →Token-based setup available for sandboxes and automation
Codex checks the spec first — then writes the code.
Point Codex at a task and it can pull the product spec, the architecture decision record or the migration guide from Perfect Wiki, build against it, and record the outcome in the wiki when the work is done.
- →Implements features against the spec your PM actually wrote
- →Respects past architecture decisions instead of re-litigating them
- →Leaves release notes and decision logs behind in the wiki
How to connect Perfect Wiki to OpenAI Codex.
- 1In your terminal, run
codex mcp add perfect-wiki --url https://api.perfectwiki.xyz/mcp - 2Codex opens a browser window. Sign in to Perfect Wiki, choose the knowledge bases and the access level, then click Allow access.
- 3Prefer a UI? In the Codex app go to Settings → MCP servers → Add server; in the IDE extension use the gear menu → MCP servers.
- 4If the session expires, run
codex mcp login perfect-wikito sign in again.
More details in the Perfect Wiki MCP server guide and OpenAI Codex's MCP documentation.
Export PERFECT_WIKI_TOKEN with a token from your knowledge base settings — Codex reads it from the environment, so the secret never sits in config.toml. The CLI equivalent is codex mcp add perfect-wiki --url … --bearer-token-env-var PERFECT_WIKI_TOKEN.
What your team does with Perfect Wiki in OpenAI Codex.
Build straight from the spec
Product specs and acceptance criteria live in Perfect Wiki. Codex reads them directly, so the implementation matches what was agreed — not a paraphrase in a ticket.
Honor architecture decisions
Codex consults your ADRs before choosing a library, a queue or a data model, and flags when a request conflicts with a recorded decision.
Write the release notes for you
When a change is ready, Codex summarizes it into release notes or a migration guide and creates the page in the right knowledge base.
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 →- Commercial CleaningDeep Cleaning SOP Template
- Commercial CleaningFloor Cleaning and Mopping SOP Template
- Commercial CleaningJanitorial Closet and Equipment Care SOP Template
- Commercial CleaningMove-Out Cleaning SOP Template
- Commercial CleaningOffice Cleaning SOP Template
- Commercial CleaningRestroom Cleaning SOP Template
Frequently asked questions
No. All three read the same ~/.codex/config.toml, so a server added with codex mcp add in the terminal also shows up in the IDE extension and the Codex desktop app.
Run codex mcp login perfect-wiki. Codex reopens the browser sign-in so you can authorize the knowledge base again.
Yes. Add bearer_token_env_var = "PERFECT_WIKI_TOKEN" to the [mcp_servers.perfect-wiki] entry and export the variable, or pass --bearer-token-env-var PERFECT_WIKI_TOKEN to codex mcp add. This suits CI jobs and sandboxes where a browser sign-in isn’t possible.
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, OpenAI Codex 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. OpenAI Codex 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 OpenAI Codex 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 OpenAI Codex.
Keep your SOPs, manuals and FAQs in Perfect Wiki — and give your whole team answers right where they work.