Pagelive for Codex
Publish what Codex builds as a tracked link.
Specs, reports, dashboards and prototypes, sent to colleagues and clients as one private link. Add Pagelive to config.toml once, then ask Codex to publish. It updates the page at the same URL when the work changes.
Free for 2 public pages. Start your 10-day trial, cancel anytime.
Setup
Connect Codex in three steps
Pagelive is a remote MCP server. Nothing to install.
Create an API key
In the Pagelive dashboard, open API & MCP and create a key. It starts with pl_ and is shown once.
Add the server
Put the block below in ~/.codex/config.toml, or in a trusted project’s .codex/config.toml. Codex sends the key from PAGELIVE_API_KEY as a Bearer token.
Ask it to publish
“Publish the dashboard you built as a Pagelive page.” Codex calls publish_page and gives you the link.
[mcp_servers.pagelive]
url = "https://app.pagelive.io/api/mcp"
bearer_token_env_var = "PAGELIVE_API_KEY"export PAGELIVE_API_KEY="pl_your_key"
codexCreate the key under API & MCP in the dashboard. Or hand the whole job to the agent: pagelive.io/agent-setup.md is written for it to follow: paste Fetch https://pagelive.io/agent-setup.md and follow the instructions. into Codex, the same line the dashboard’s Copy setup prompt button copies.
The flow
Publish, get the link, update at the same URL
Publish
Ask your agent to publish the HTML it built. It calls publish_page with the document and a title.
Get the link
The result holds the url to send and the slug to keep. The page is live, kept out of search by default, and tracked.
Update at the same URL
When the page changes, the agent calls update_page with the slug. The link never changes, so nobody needs a new one.
The review loop
Teammates and clients comment on the page. Codex makes the change.
Readers comment on the text, pin an element, suggest the exact wording, or approve and request changes. Codex reads the open threads with list_comments, applies suggested edits with apply_suggestion, and closes what it fixed by passing the thread ids to update_page in resolves. list_decisions tells it who approved.
> Fix the comments on
the Q3 report.
list_comments q3-report
→ 3 open threads
apply_suggestion c_81
→ applied, saved as v5
update_page q3-report
resolves: [c_79, c_80]Tools
What Codex can call
All 19 tools the Pagelive MCP server registers, one line each.
publish_page Publish an HTML document and get its link back.
update_page Change a page at the same URL, with targeted edits or a full rewrite.
list_pages List your pages with their links, folders and view counts.
get_page_stats Views, unique viewers and top countries for one page.
list_form_submissions Read the replies sent through a form on a page.
create_recipient_link Give one person their own link, so their opens show under their name.
list_recipient_links The recipient links on a page, each with its opens and reading time.
list_comments Read the comments people left on a page, with the text or element each one points at.
create_comment Start a comment thread on a page, or an internal note only your team sees.
reply_comment Reply to a comment thread; the commenter gets it by email.
resolve_comment Mark a comment thread resolved once the page addresses it.
apply_suggestion Apply a suggested edit to the page and close its thread.
reopen_comment Reopen a resolved comment thread.
list_decisions Who approved a page and who requested changes, with their notes.
list_workspaces Your personal workspace and any teams, to publish into.
list_domains Your connected custom domains, to publish onto.
list_folders The folders in a workspace, with page counts.
create_folder Create a folder to group related pages.
move_page File a page into a folder, or back to the root.
Codex FAQ
Yes. The Codex CLI and the IDE extension read the same config.toml, so one entry covers both.
bearer_token_env_var tells Codex which variable holds the token, so the key never sits in config.toml. Anyone with the key can publish to your account, so keep it out of files you share.
Yes. Point it at pagelive.io/agent-setup.md. The file covers the server URL, the key header, every tool, and the publish, link, update flow, written for an agent to follow.
No. A Pagelive link opens in any browser, with no account. They only see a password or email prompt if you add one.
Using another agent? Setup for Claude Code and Cursor. Calling the API from a script? See Pagelive for AI agents.
Let Codex send its work as a tracked link.
Three lines of config to connect. Noindex by default. Free for 2 public pages.