How to connect Firecrawl to Codex

  • Codex gets 40 Firecrawl tools through one Metorial MCP URL.
  • Setup is 3 steps; teammates then sign in with SSO.
  • You need the Codex CLI, IDE extension or ChatGPT desktop app.

What Codex can do with Firecrawl

Ask your agent in plain language. Each of these maps to a real tool on the server.

  • Ask Codex to use the get credit usage tool in Firecrawl
  • Ask Codex to use the create browser session tool in Firecrawl
  • Ask Codex to use the get monitor check tool in Firecrawl
  • Ask Codex to use the list activity tool in Firecrawl
  • Ask Codex to use the run monitor tool in Firecrawl

Add the Firecrawl MCP server to Codex

Run these once. Afterwards, everyone you give access to signs in the same way.

  1. 1. Enable Firecrawl in Metorial

    In your Metorial portal, enable the Firecrawl 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.

    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 Firecrawl tools.

Give your team Firecrawl in Codex

Once Firecrawl is enabled in Metorial, teammates sign in with SSO and get the same connection in Codex, with only the tools their role allows.

One link covers every app you approve. See how the MCP gateway handles access, roles and audit logs for the whole company.

Firecrawl tools available in Codex

Full descriptions and inputs are on the Firecrawl MCP server page.

  • Extract Data: Start a Firecrawl v2 extraction job that uses AI to transform one or more web pages into structured data.
  • Map Website: Map a website with Firecrawl v2 and retrieve discovered URLs quickly.
  • Crawl Website: Start a Firecrawl v2 crawl job to recursively discover and scrape pages from a website.
  • Get Agent Status: Check a Firecrawl agent job and retrieve gathered data when complete.
  • Run Agent: Start a Firecrawl v2 agent job for autonomous web data gathering.
  • Get Extract Status: Check a Firecrawl extract job and retrieve structured data when complete.
  • Get Batch Scrape Status: Check a Firecrawl batch scrape job and retrieve available page data.
  • Scrape Page: Scrape a single URL with Firecrawl v2 and extract markdown, HTML, raw HTML, links, screenshots, images, audio/video URLs, structured JSON, summaries, brand data, answers, highligh…
  • Get Crawl Status: Check a Firecrawl crawl job and retrieve available page data.
  • Batch Scrape: Start a Firecrawl v2 batch scrape job for a known list of URLs.
  • Search Web: Search the web with Firecrawl v2 and optionally scrape search results.
  • Get Crawl Errors: Retrieve failed URLs and robots.txt blocked URLs for a Firecrawl crawl job.
  • Parse File: Upload a file to Firecrawl v2 Parse and convert it into markdown or other extraction formats.
  • Cancel Crawl: Cancel a running Firecrawl crawl job.
  • Interact With Page: Continue interacting with the browser state from a prior Firecrawl scrape.
  • And 25 more on the Firecrawl MCP server page.

Using Firecrawl tools in Codex

What to expect once Firecrawl is connected.

  • Limit which Firecrawl 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 Firecrawl tool with tools.<tool>.approval_mode.

Troubleshooting Codex

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.

Frequently asked questions

Common questions about connecting Firecrawl to AI agents with Metorial.

  1. Does Codex support the Firecrawl MCP server?
    Yes. Codex connects to the Firecrawl MCP server through one CLI command, pointed at your Metorial URL. You need the Codex CLI, IDE extension or ChatGPT desktop app.
  2. No. You sign in to Firecrawl once through Metorial, and Codex uses that connection. No API keys go into Codex's settings.
  3. All 40 Firecrawl tools your team allows, such as Extract Data, Map Website, Crawl Website. Admins can narrow that list per team.
  4. Yes. Role-based access control decides who can use Firecrawl and which of its tools appear in Codex, and every call is logged with the person's identity.
  5. Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.