Agent MCP

Firecrawl Agent MCP lets agents connect to Firecrawl through a remote MCP server in tools like Codex, Claude Code, Cursor, or other MCP clients. It supports keyless access to start, with an API key unlocking more usage and broader tool availability.

AI代理開發 AI開發者工具

訪問網站

Managed MCP access for Firecrawl

Firecrawl Agent MCP is the managed MCP connection option for Firecrawl. It is designed to let AI agents connect to Firecrawl from MCP-capable tools such as Codex, Claude Code, Cursor, or another agent harness without requiring a local server setup.

The page frames Agent MCP as the fastest way to get started: agents can connect instantly in keyless mode, then add a Firecrawl API key when they need more usage or broader tool access. The connection uses the hosted Firecrawl MCP endpoint, and the documentation focuses on getting that endpoint working in a client, confirming the connection, and understanding what tools are available in each access mode.

What Agent MCP provides

Hosted MCP endpoint

Connect to the remote Firecrawl MCP server at a single hosted URL instead of running the server locally. This is the setup path shown for Codex, Claude Code, Cursor, and other MCP clients.

Keyless startup

Agents can begin using the service without an API key. The docs note that keyless access is rate limited and exposes a smaller tool set.

API key support

Users can add a Firecrawl API key as a bearer token to unlock more usage and, depending on plan and policy, the full tool surface.

Client-specific setup examples

The page provides concrete connection examples for Codex, Claude Code, Cursor, and OpenCode, including commands or configuration snippets.

Connection verification guidance

The docs explain how to confirm that the MCP server is connected in the client and what tool names should appear for keyless versus authenticated access.

Tool surface disclosure

The page explains that keyless access exposes firecrawl_search, firecrawl_scrape, and firecrawl_parse, while authenticated connections can expose additional tools subject to deployment and policy.

When to use Agent MCP

Getting an agent connected quickly
Use Agent MCP when you want to point an MCP client at Firecrawl with minimal setup and no immediate API key requirement.
Testing Firecrawl in an AI coding tool
Use it to connect Firecrawl inside Codex, Claude Code, Cursor, or OpenCode and verify that the client can see Firecrawl tools.
Starting with limited access before upgrading
Use keyless mode to try Firecrawl first, then add an API key if you need higher limits or more tools.
Wiring Firecrawl into an agent workflow
Use the hosted endpoint when your workflow is centered on an agent harness and you do not need to manage a local MCP process.

Pros and Cons

Pros

No API key is required to start.
Works with multiple MCP clients, including Codex, Claude Code, Cursor, and OpenCode.
The docs show explicit connection and verification steps.
Adding an API key can increase usage and expand tool availability.
The hosted setup avoids local server installation for the managed path.

Cons

Keyless access is rate limited.
The page does not provide pricing details.
Tool availability can vary by plan, deployment, and team policy.
The documentation shown here is setup-focused and does not describe every workflow in depth.

FAQ

Do I need an API key to use Agent MCP?

No. The docs say agents can start instantly in keyless mode. An API key is optional at first and can be added later to unlock more usage.

Which tools are available without an API key?

The page says keyless access exposes firecrawl_search, firecrawl_scrape, and firecrawl_parse.

How do I connect Firecrawl in Cursor or Claude Code?

The page provides setup examples for each client. In general, you add the hosted MCP URL to the client’s MCP configuration and then confirm that Firecrawl is connected.

What should I check if the tools do not appear?

The docs advise reloading or restarting the client after saving MCP settings, then checking the client’s MCP status or tool list.

Is Agent MCP the same as running Firecrawl locally?

No. The local MCP page describes a separate local server option for stdio or Streamable HTTP, while Agent MCP is the managed hosted connection.

Quick Facts

Category: Developer Tool
Product type: Managed MCP server for Firecrawl
Primary users: AI agents and developers using MCP clients
Supported clients mentioned: Codex, Claude Code, Cursor, OpenCode
Access modes: Keyless and API-key-authenticated
Source domain: docs.firecrawl.dev