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.

Connect Context.devSee the setup

7 days free · 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

FirstConnect Context.dev to ApexGenius

ThenConnect ApexGenius to Codex

Context.devmcp.context.dev/authorize1 of 3

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

Then ask Codex:

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

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

  1. In the desktop app, open Settings, then MCP servers and Add server.
  2. Name the server ApexGenius, choose Streamable HTTP, and paste the MCP address above.
  3. Save, then select Restart. Choose Authenticate for ApexGenius and complete the browser sign-in.
  4. When ApexGenius asks what this AI client may use, choose Read only for the first test, or Custom to limit it to the tools you need.
  5. Start a new conversation and select ApexGenius from the available tools before asking for live data.
Official Codex setup instructions ↗

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)

Step 1 of 4Open Plugins

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.

OpenAI Plugins guide (opens in a new tab)Full Codex setup guide
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.

What Codex can do in Context.dev

34 operations. Read looks things up and changes nothing. Write changes Context.dev and runs only when that tool is enabled.

Read27 operations

Looks things up. Changes nothing.

Search and read pages

  • web-searchSearch the live web and optionally return ranked results as Markdown.
  • web-scrape-markdownTurn one known URL into clean Markdown. The default way to read a page.
  • web-scrape-htmlReturn the raw HTML of one URL when the markup itself matters.
  • web-scrape-imagesList the images on one page, with sources and available metadata.
  • web-screenshotCapture a rendered PNG of a page, full page or one viewport.

Map, crawl and extract

  • web-scrape-sitemapList a site's URLs from its sitemap without reading every page.
  • web-crawlFollow links from one URL and return Markdown for several pages in one call.
  • web-extractCrawl the relevant pages and return JSON shaped by the JSON Schema you pass.

Documents

  • parse-documentConvert PDF, Office, spreadsheet, image or text file bytes into Markdown.

Company and brand data

  • get-brandShow a company's logo, colors, description, links and social profiles for one domain.
  • brand-retrieve-unifiedReturn brand data as JSON by domain, name, work email, ticker, ISIN, transaction text or URL.
  • web-styleguideRead a site's colors, type, spacing and shadows.
  • web-fontsName the font families a site uses, with fallbacks.
  • web-naicsClassify a company into 2022 NAICS industry codes.
  • web-sicClassify a company into SIC industry codes.

Monitor history

  • list-monitorsList the monitors in your organization with status and tags.
  • get-monitorRead one monitor's target, schedule, rules and webhook settings.
  • list-monitor-runsList one monitor's runs with status, timing and credits.
  • get-monitor-runRead one run and the change it found, if any.
  • list-account-runsList monitor runs across the whole organization.
  • list-monitor-changesList the changes one monitor has found.
  • list-changesList changes found across all monitors.
  • get-changeRead one change with its text diff, evidence and importance.
  • list-monitor-credit-usageReport credits spent by each monitor over a time window.

Batches

  • list-batchesList batch jobs from newest to oldest.
  • get-batchRead one batch's status, progress and credit use.
  • get-batch-resultsPage through a finished batch's results as JSON.

Write7 operations

Changes Context.dev. Runs only when enabled.

Manage monitors

  • create-monitorCreate a recurring monitor. It runs a first baseline right away and spends credits on each later run.
  • update-monitorChange or pause a monitor. A new target or rule starts a new baseline.
  • run-monitor-nowStart a check now. It spends credits and can send the monitor's webhook.
  • delete-monitorPermanently delete a monitor and its future runs. Cannot be undone.

Batches

  • submit-batchStart a background scrape or crawl job. It can call an outside webhook when done.
  • cancel-batchStop a batch from starting new pages. Stored results are kept.
  • delete-batchPermanently delete a finished batch and its stored results. Cannot be undone.

You choose what Codex can use

When you approve Codex, pick Full access, Read only, or Custom. Read only allows the Read operations and nothing else. Custom picks apps and tools one by one.

Limits in Context.dev

  • · 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.

What it looks like in Codex

An illustrative read-only request and response. Your results 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

Try asking

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

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

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

“Search the web for this week's official Stripe product announcements and cite each source URL.”

More connections like this one

One ApexGenius account covers every pair below. Connect an app once and each agent you allow can use it.

Questions people ask first

How do I connect Context.dev?

Open Context.dev in ApexGenius Connections, choose Connect, and sign in to Context.dev in the browser. ApexGenius registers itself with the hosted Context.dev MCP. No API key is pasted into ApexGenius.

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

7 days free. No card required. Disconnect any time.