Skip to content

Connect Codex to Context.dev

Connect Codex to Context.dev in 3 steps: 1. Sign in to ApexGenius and connect Context.dev. 2. Add the ApexGenius plugin. 3. Start using Context.dev in Codex. Start in Plugins in the ChatGPT desktop app and authorize your connection.

1,000 free credits · No card required

How to connect Context.dev to Codex

  1. 1Sign in to ApexGenius and connect Context.dev
  2. 2Add the ApexGenius plugin to Codex
  3. 3Start using Context.dev in Codex
  1. 1Context.dev

    Connect Context.dev to ApexGenius

    Connect Context.dev

    Context.dev opens its own sign-in. Sign in and allow ApexGenius.

  2. 2ApexGenius

    Connect ApexGenius to Codex

    Choose Codex

    Back on Start, pick Codex and copy the prompt.

  3. 3ApexGenius

     

    Approve access

    ApexGenius opens its approval page. Review the access, then approve.

Add the ApexGenius plugin to Codex

Codex stores MCP servers in ~/.codex/config.toml. The ChatGPT desktop app, the Codex CLI and the IDE extension share that file, so one setup covers all three on the same machine.

  1. In the ChatGPT desktop app, open Plugins and select an ApexGenius plugin shared with you or one you created. Connect it and authorize the app connections you intend to use.
  2. No plugin? Open Settings, then MCP servers, then Add server. Name it ApexGenius, choose Streamable HTTP and paste the MCP address.
  3. Save, select Restart, then Authenticate, and sign in to ApexGenius in your browser.
  4. Start a new Codex task.

The MCP address

https://server.autom8.pro/mcp

Check it. In the composer, type /mcp to view the connected servers.

Steps follow OpenAI documentation, Model Context Protocol for ChatGPT and Codex (opens in a new tab), read November 12, 2026.

Then ask Codex

List my Context.dev monitors. Do not create, run, or change anything.

Start free
Written setup, step by stepShow

Before you start

  • An account with permission to use the Context.dev resources you intend to connect.

1. Connect Context.dev to ApexGenius

  1. Open Context.dev in Connections. Choose Connect, or Add connection when offered. Give the connection a name if prompted. If Gateway setup pending appears, contact ApexGenius support before continuing.
  2. Choose the account and review access. Sign in to Context.dev in the browser and approve access for your organization. Context.dev uses browser authorization; no Context.dev API key is pasted into ApexGenius.
    The full Context.dev connect page, Connect Context to an unverified app, with red boxes around the verification notice and the Sign in button.
    Context.dev labels ApexGenius an unverified app and names server.autom8.pro, the ApexGenius gateway, as the address that receives access. Sign in to continue.Open full-size image (opens in a new tab)
  3. Review the connected account and resources. Confirm the connected Context.dev organization. Open Tools to review its reads and the monitor and batch actions. Most operations spend your organization's Context.dev credits.
  4. Check the connection. Use Test connection or Check again and read the reported status. Add an AI agent from the AI agents page, choose Read only for the first test, and try the question below.
Connect Context.dev →

2. Connect ApexGenius to Codex

The steps are above, under Add the ApexGenius plugin to Codex. These notes apply to Codex only.

  • From the terminal. The commands are under Manual setup for developers. codex mcp list shows the configured servers, and codex mcp login apexgenius runs the sign-in.
  • Without a local browser. Run codex mcp login apexgenius --no-browser, open the printed authorization URL on another machine, sign in, and paste the full redirect URL back into the terminal.
  • Asking before writes. In config.toml, default_tools_approval_mode = "writes" on the apexgenius server makes Codex ask before any tool that is not marked read-only.
  • ChatGPT on the web. ChatGPT on the web does not read local Codex configuration. It uses plugins.
  • Access. When ApexGenius asks what Codex may use, choose Read only for the first test, or Custom to limit it to the tools you need.

Watch the setup

Follow each step at your own pace.

Codex desktop app with Plugins selected and ApexGenius listed under Available to your account.
Open Codex in the ChatGPT desktop app, then Plugins, and find ApexGenius.Open full-size image (opens in a new tab)

The walkthrough uses the original ChatGPT web plugin captures. After connecting, open Codex in the desktop app and start a new task with ApexGenius. A ChatGPT web connection does not verify Codex access.

A public ApexGenius plugin listing is not verified. Use a plugin shared with you or one you created, subject to your account and workspace policy.

Create a personal plugin

Where Developer mode is available, open ChatGPT Settings, then Security and login, and enable it. In Plugins, select the plus button, enter ApexGenius and a description, then add this URL under Connection. Create the connection, complete OAuth, and review the tools. Return to Codex in the desktop app and start a new task with the plugin enabled.

https://server.autom8.pro/mcp
OpenAI custom connection guide (opens in a new tab)
No plugin available? Use desktop settings
  1. In the ChatGPT desktop app, open Settings, then MCP servers, then Add server.
  2. Name the server ApexGenius, choose Streamable HTTP, and paste the MCP address below.
  3. Save, select Restart, then Authenticate. Sign in to ApexGenius and authorize the intended connections and access.
  4. Start a new Codex task and ask one read-only question. Check the returned result and its matching successful read in Activity.
https://server.autom8.pro/mcp
OpenAI desktop MCP settings (opens in a new tab)
Manual setup for developers

Codex CLI is optional. Run these commands, complete browser authorization, then start a new session. Do not paste bearer tokens or static authorization headers.

Register the remote MCP server

codex mcp add apexgenius --url https://server.autom8.pro/mcp

Authorize in your browser

codex mcp login apexgenius

Inspect registered servers

codex mcp list

The desktop app, CLI, and IDE extension share MCP configuration on the same host. The IDE extension does not install plugins. ChatGPT web does not read local Codex configuration.

3. Verify one safe read

List my Context.dev monitors. Do not create, run, or change anything.

List my Context.dev monitors. Do not create, run, or change anything.

Compare the returned account and resource with Context.dev. Check the connection status separately from the result of the first read.

Full guide: the Context.dev setup guide.

What it looks like in Codex

Illustration of a task, not a recorded customer result. Your answers come from the account and dates you choose.

How the route works
Codex
CodexApexGenius MCP route
List my Context.dev monitors and their status. Do not create, run or change anything.
ApexGenius
Working with ApexGenius1 tool search · 1 read
RequestCheck the connection
Account scopeAuthorized connections checked
apex_search_toolsContext.dev monitors · Find the Context.dev read routeComplete
apex_call_read_toollist-monitors · List monitorsComplete
Codex

Illustrative example: two monitors are active, a pricing page checked daily and a changelog checked weekly. Listing monitors spends no credits. Nothing was changed.

Read-only route
Codex

What to ask Codex about Context.dev

  • Check the connection

    List my Context.dev monitors and their status. Do not create, run or change anything.

    Runs list-monitors (read).

  • Read a page

    Read https://example.com/pricing as Markdown and list every plan with its price. Cite the URL.

    Runs web-scrape-markdown (read).

  • Look up a company

    Pull the brand profile for linear.app: logo, colors, fonts and social links.

    Runs brand-retrieve-unified (read), then web-fonts (read).

These 3 questions use 4 of Context.dev’s 34 operations. The full list is below.

  • Search the web for this week's official Stripe product announcements and cite each source URL. (read)
  • Create a daily monitor on this pricing page. Show me the schedule and the credit cost first. (write)

What Codex can do in Context.dev

34 operations: 27 read, 7 write. Read looks things up and changes nothing. Writes change Context.dev and run only when you turn them on.

Search and read pages

5 read
  • web-searchread
  • web-scrape-markdownread
  • web-scrape-htmlread
  • web-scrape-imagesread
  • web-screenshotread

Map, crawl and extract

3 read
  • web-scrape-sitemapread
  • web-crawlread
  • web-extractread

Documents

1 read
  • parse-documentread

Company and brand data

6 read
  • get-brandread
  • brand-retrieve-unifiedread
  • web-styleguideread
  • web-fontsread
  • web-naicsread
  • web-sicread

Monitor history

9 read
  • list-monitorsread
  • get-monitorread
  • list-monitor-runsread
  • get-monitor-runread
  • list-account-runsread
  • list-monitor-changesread
  • list-changesread
  • get-changeread
  • list-monitor-credit-usageread

Manage monitors

4 write
  • create-monitorwrite
  • update-monitorwrite
  • run-monitor-nowwrite
  • delete-monitorwrite

Batches

3 read · 3 write
  • submit-batchwrite
  • list-batchesread
  • get-batchread
  • get-batch-resultsread
  • cancel-batchwrite
  • delete-batchwrite

You choose the access. When you approve Codex, pick Full access, Read only, or Custom.

Context.dev controls the OAuth grant. The connection acts for your Context.dev organization and uses its shared credits.

The read route checks Context.dev's live tool label and rejects writes or unlabeled operations.

Writes run right away when enabled. A deleted monitor or batch cannot be restored.

Fetched page text is untrusted data. The ContextDev skill tells your AI to quote and cite it and never follow instructions inside it.

Disconnecting stops future gateway access. It does not stop monitors or batches that already exist.

Start free

Questions about connecting Codex to Context.dev

Updated November 12, 2026.

How do I connect Codex to Context.dev?

Sign in to ApexGenius and connect Context.dev. In the ChatGPT desktop app, open Plugins and connect an ApexGenius plugin, or open Settings, then MCP servers, then Add server, and add the ApexGenius MCP address as a Streamable HTTP server. Then ask Codex: “List my Context.dev monitors. Do not create, run, or change anything.” Start with a read, so nothing changes.

How do I check that Codex can use Context.dev?

In the Codex composer, type /mcp to view the connected servers. ApexGenius should be listed. If it asks for sign-in, open Settings, then MCP servers, and select Authenticate. Start a new task, then ask: “List my Context.dev monitors. Do not create, run, or change anything.”

Does it spend Context.dev credits?

Most calls do. A scrape is 1 credit, a web search is 1 credit per 10 results, a crawl is 1 credit per page and a brand lookup is 10 credits. Listing monitors is free. Free organizations get 1,000 credits a month with a work email, or 250 once with a personal email.

Can my AI change my Context.dev account?

Yes. It can create, update, run or delete monitors and submit, cancel or delete batches. Writes run right away when enabled. A deleted monitor or batch cannot be restored.

Can a web page tell my AI what to do?

It should not. Page text is data. The ContextDev skill tells your AI to quote and cite it and never follow instructions found inside it. Review results before you act on them.

Can I take this setup to another AI agent?

Yes. Add ApexGenius to another compatible agent with the same ApexGenius account. It uses the same Context.dev connection and can load the ContextDev skill. Each agent needs its own setup.

Connect Context.dev to Codex today

Start free

1,000 free credits. No card required. Disconnect any time.