Connect Codex

Use IPGuru from Codex

The Codex CLI, the desktop app and the IDE extension share one configuration. Add IPGuru once, sign in, and Codex can create scenarios, work with the crew, make documents and images, and run Scenario Director.

Tested by IPGuru, September 2026

Add IPGuru

From the terminal or the app

Add the server

From a terminal with Codex installed:

codex mcp add ipguru --url https://mcp.ipguru.ai/mcp

Or, in the desktop app or the IDE extension, open Settings, then MCP servers, then Add server. Name it ipguru, choose Streamable HTTP, paste the address, save, then Restart. Labels can differ between versions.

Sign in

Adding the server may start sign-in on its own. If it does not, run:

codex mcp login ipguru

In the app, choose Authenticate. Do not start a second sign-in while the first is waiting.

Approve on IPGuru

Your browser opens IPGuru's sign-in page. Sign in with the account that owns your work. Check that the page names Codex and lists Read, Write and Spend, then choose Continue. No password or key goes into Codex.

Check it

codex mcp get ipguru shows the saved entry. In the app, reload the IPGuru server after signing in if the tools do not appear.

Configuration file

If you prefer to edit it yourself

Codex keeps MCP servers in ~/.codex/config.toml, used by every project. A project's own .codex/config.toml works in projects you trust.

[mcp_servers.ipguru]
url = "https://mcp.ipguru.ai/mcp"

Then run codex mcp login ipguru. OpenAI's Codex MCP guide covers the other settings.

The IPGuru skill

Teach Codex how IPGuru works

The skill tells Codex how a crew turn works, when to ask before spending, and how to recover after a lost reply without paying twice.

  1. Download ipguru-skill.zip.
  2. Unzip it into ~/.agents/skills/, so the main file is at ~/.agents/skills/ipguru/SKILL.md. For one repository only, use that repository's .agents/skills/ folder.
  3. Mention $ipguru in a prompt, or just mention IPGuru. The skill also tells Codex that it needs the IPGuru MCP server.

Your first session

What to say to Codex

Start with the read-only check. Then create a scenario and work on it. Replace the parts in square brackets.

fact_check

Check the connection

Say to CodexUse IPGuru to open my session and list my scenarios with their saved Idea scores, freshness and app links. Keep this check read-only.

Compare the list with what you see in the app. An empty list is fine for a new account.

add_circle

Create a prepared scenario

Say to CodexCreate a prepared IPGuru scenario for [your idea]. Use the same preparation as the New Scenario wizard. Keep my theme, frame, intent and chosen experts. Return the app link and the preparation status.

Preparation runs on IPGuru's servers and carries on if you close Codex. It can use allowance.

groups

Work with the crew

Say to CodexBrainstorm this with the seated experts. Then ask the same experts to critique the result. Name the biggest gaps, and keep their proposals separate from verified evidence.
description

Make and check documents

Say to CodexList the document packs I can make for this scenario. Make [a pack], read it in full and check it against the current Idea before accepting it.
image

Make images

Say to CodexUse this scenario's Studio to make a product sheet and a hero image. Keep the product consistent, look at each result, and tell me what you checked.
route

Run Scenario Director

Say to CodexSet up Scenario Director for this scenario to achieve [your objective]. Keep [your constraints] and use supervised mode. Show me the saved plan before you start it.

Approving the plan starts paid work. Codex should wait for your go-ahead.

Troubleshooting

Codex and IPGuru

  • No IPGuru tools. Check the server is enabled, the address ends in /mcp, and you reloaded it after signing in.
  • The wrong scenarios. Sign in again with the IPGuru account that owns the work.
  • scope_required. Sign in again and allow the permission named in the message.
  • Preparation stopped part way. Ask Codex to read the saved progress first, then resume it. Completed stages are kept. Codex should reuse the original request, not start a new scenario.
  • A stale revision or preview. Something changed since Codex last read it. Ask Codex to reload and review the current record.
  • An allowance refusal. Keep your limits. Connecting Codex does not add allowance.
  • A certificate warning. Check the address is exactly mcp.ipguru.ai and contact us. Never turn off HTTPS checks.
  • If the app still shows an older state after Codex changed something, refresh the page.