Codex App integration
Codex is OpenAI's agentic coding tool. It reads and edits your codebase, runs commands, and completes multi-step development tasks.
The Apify plugin for Codex connects Codex to Apify's library of Actors and bundles:
- The Apify MCP server for searching Apify Store, running Actors, and retrieving datasets through the Model Context Protocol (MCP).
- Five built-in skills for common workflows (see Bundled skills below).
This guide covers installation in the Codex app.
This integration uses a third-party service. If you find outdated content, please submit an issue on GitHub.
Prerequisites
- An Apify account - sign up for free if you don't have one.
- Codex - installed.
Install the plugin
-
In Codex, open the sidebar and select Plugins.
-
On the Plugins screen, select the dropdown next to + and choose Add marketplace.

-
In the Add plugin marketplace dialog, enter the Apify plugin repository in the Source field:
apify/apify-codex-plugin
-
Select Add marketplace.
-
On the Plugins screen, open the Personal tab. The Apify plugin appears under Apify Plugin.

-
Select Add next to Apify.
-
In the dialog, select Add to Codex.
-
Select Install Apify to start the Apify MCP server setup.
Authenticate to Apify
The plugin bundles the Apify MCP server. Read-only tools like searching Apify Store and fetching Actor details work without signing in, but you need to authenticate to run Actors and access your account data.
-
After you select Install Apify, Codex starts the Apify MCP server setup and opens a browser tab for the Apify OAuth flow.
-
Review the permissions and click Allow access.
-
Back in Codex, the
apifyMCP server connects and is ready to use.
The connection stays authenticated for future sessions. You can revoke access at any time in Apify Console > Settings > Integrations.
Run your first prompt
Describe what you want in natural language. Because this bundle exposes the MCP tools and skills directly, be explicit about the workflow you want.
Use Apify to find a good Actor for scraping Google Maps places. Show me the best option, its input requirements, pricing model, and what kind of dataset output it returns. Do not run the Actor yet.
Codex searches Apify Store, fetches the top Actor's details through the apify MCP server, and summarizes its inputs, pricing, and output - all without running the Actor.

Bundled skills
| Skill | Description |
|---|---|
apify-ultimate-scraper | CLI-driven extraction using existing Actors for multi-step scraping and lead-generation workflows. |
apify-actor-development | Full Actor lifecycle - template selection, development, local testing, and deployment with apify push. |
apify-actorization | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. |
apify-generate-output-schema | Generates dataset and key-value store schemas for existing Actors. |
apify-sdk-integration | Integrates Actor execution into applications using the apify-client package. |
Example prompts that route to specific skills:
Ultimate scraper:
Find 10 highly rated coffee shops in Seattle with name, address, rating, phone, and website.
Actor development:
Create an Apify Actor that accepts a
startUrlandmaxPagesinput, crawls the site, and stores each page title and URL.
SDK integration:
Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON.
Troubleshooting
The Apify plugin does not appear in the list
Open the Plugins screen, switch to the Personal tab, and confirm the Apify marketplace was added. If the Apify plugin still doesn't appear, re-add the marketplace using the repository apify/apify-codex-plugin.
The Plugins screen does not appear
Plugins require a local installation of Codex with plugin support enabled. Install or update Codex, then reopen the Plugins screen.
Browser doesn't open, or OAuth fails
If the browser doesn't open automatically, copy the OAuth URL shown by Codex and paste it into your browser manually.
If you're running Codex in a headless environment (SSH, remote container) or the OAuth flow still fails, authenticate with an API token instead. Copy your token from Apify Console > Settings > Integrations and set it before starting Codex:
export APIFY_TOKEN=<YOUR_API_TOKEN>
Limitations
- Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts.
- Each Actor run consumes Apify platform usage from your plan in addition to any Codex usage. See Billing for details.
- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing.
Related integrations
- MCP server integration - Use the Apify MCP server with other clients
- ChatGPT integration - Connect the Apify MCP server to ChatGPT
Resources
- Apify plugin for Codex - Source repository and full README with advanced setup notes (Apify CLI install, all auth paths, available MCP tools)
- Codex documentation - Official Codex docs
- Apify Store - Browse Actors you can run from Codex