Before you start
- A Popcorn role with the API Keys → View permission, so you can open Settings → AI Assistants. The built-in Owner, Admin, and Manager roles have it.
- Codex CLI installed on your computer.
- You will need to sign in to Popcorn in the browser during approval.
Connect
1
Copy the commands
In Popcorn, go to Settings → AI Assistants. Under Assistant setup, find the Codex card labelled Codex CLI and click Copy commands. The commands are:
2
Register Popcorn
Run the first command. It adds Popcorn to Codex as a server named
popcorn.3
Sign in and approve
Run the second command. Codex opens the Authorize Popcorn MCP screen in your browser. If you are not signed in to Popcorn, you are sent to sign in first and then brought back.The screen shows the Client (the assistant asking), the Workspace it will reach, when the request Expires, and a Requested access list with one line per area. Check that the workspace is the one you intend, then click Allow access. Return to your terminal.
4
Try a request
Ask Codex something read-only first, for example “Give me an overview of my Popcorn workspace” or “Show my last five orders.”
The approval request is valid for 10 minutes and can be used once. If you see Authorization request expired. (also shown when a link is reopened after it was already approved or denied), run
codex mcp login popcorn again.What the approval screen means
- Requested access lists each area Codex asked for. Lines such as Read campaign workspace data or Create and manage campaigns describe what that area allows. Anything marked as needing “an explicit confirmation plan” means Codex must show you a preview and get your go-ahead each time before Popcorn carries it out.
- If Codex does not ask for specific areas, Popcorn grants read-only access across the workspace.
- Access never exceeds your own Popcorn role. If the request asks for more than your role allows, approval fails with a message starting Your Popcorn role cannot grant MCP scopes.
- Deny cancels the request. Nothing is connected.