How to connect Apify to Codex

1. 1. Enable Apify in Metorial

   In your Metorial portal, enable the Apify MCP server and sign in with the account that owns the data. Access stays governed by your team policies.

2. 2. Add the server and sign in

   The Codex CLI, IDE extension and ChatGPT desktop app share this config.

   Copy

   codex mcp add metorial --url <your-magic-mcp-url>
   codex mcp login metorial

3. 3. Check the connection

   Type /mcp in Codex to see Metorial and its Apify tools.

• Run Actor: Start an Apify Actor run.
• Manage Task: Create, get, update, delete, list, or run Apify Actor Tasks.
• Manage Actor: Get, create, update, or delete an Apify Actor owned by the authenticated account.
• List Runs: List Apify Actor runs either account-wide or for a specific Actor.
• Abort Run: Abort a running Apify Actor execution.
• Manage Webhook: Create, get, update, test, delete, or list Apify webhooks for Actor run and build events.
• Get Dataset Items: Retrieve or export items from an Apify dataset.
• Manage Schedule: Create, get, update, delete, or list Apify schedules that run Actors or Actor Tasks on a cron expression.
• Manage Key-Value Store: Manage Apify key-value stores and records.
• Get Run: Retrieve an Apify Actor run by ID, optionally including JSON dataset items or the run log as a Slate attachment.
• Push Dataset Items: Append JSON objects to an Apify dataset.
• Build Actor: Start an Apify Actor build, retrieve build details, or list builds for an Actor.
• List Actors: List Actors owned by the authenticated Apify account.
• Manage Request Queue: Manage Apify request queues and queued crawler requests.
• Search Store Actors: Search public Apify Store Actors.
• And 4 more on the Apify MCP server page.

• Limit which Apify tools Codex sees with enabled_tools and disabled_tools on the metorial server in config.toml.
• Set default_tools_approval_mode to auto, prompt, writes or approve. writes prompts only for tools that are not marked read-only.
• Type /mcp in the composer to see the connected servers.
• Override the approval behavior for a single Apify tool with tools.<tool>.approval_mode.

Metorial is listed but tools are missing

Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.

Metorial times out at startup

Codex waits 10 seconds by default. Raise startup_timeout_sec under [mcp_servers.metorial] in ~/.codex/config.toml.

Long tool calls fail after a minute

The default tool timeout is 60 seconds. Raise tool_timeout_sec for the metorial server in config.toml.

Based on the Codex MCP documentation.