Designed PDFs and lead magnets from Codex
Add Unplain to Codex with an API key, kept in your environment rather than a file. Codex can then create a document, have Unplain design it in your brand, export the PDF, publish it with an email form and see how it is doing.
An API key, on every plan including Free.
Set it up
A key, then one command.
The key lives in your environment; the config only names it.
Things to ask
Things to ask.
Codex writes, often from your repository. Unplain designs and publishes.
- Use Unplain to turn docs/onboarding.md into a designed guide.
- Export the release notes as a PDF in our brand.
- List the leads from this week's guide with their sources.
An example
Asked for, designed.
The kind of guide your assistant can make with Unplain.
Template · 6 pages
The yearly review
Twelve questions, one page each: a template for looking back on the year before planning the next.
A template Codex can draft from your notes, designed and exported by Unplain.
How do I connect Unplain to Codex?
Create an API key in Unplain, export it as UNPLAIN_API_KEY, then run codex mcp add unplain --url https://app.unplain.io/api/mcp --bearer-token-env-var UNPLAIN_API_KEY.
Why an environment variable?
It keeps the key out of a file you might sync or commit. Codex's config only records the variable's name.
Codex cannot find the key. Why?
Codex reads the variable when it starts. Export it in the shell you launch Codex from, add it to your shell profile, and restart Codex.
Does the key work on the free plan?
Yes. The MCP server and API keys are included on every plan, including Free.
Can Codex see who signed up?
Only if you allow it. Tick Read leads when you create the key. Without it, Codex still sees each guide's visitors, sign-ups and sources, but not names or emails.
Does Unplain write the content?
No. Codex writes, or you do. Unplain designs it and publishes it.
See also
Keep reading.
Plain docs in. Leads and data out.
Free to start. No account needed to try it.