Skip to content

Application Development

Firecrawl MCP connector

The Firecrawl connector lets Claude, ChatGPT, Cursor, and the Elaichi Agent scrape a page, crawl a whole site, map its links, or extract structured data from the web, with every request running under your Firecrawl account and recorded in an audit log.

Connect on Elaichi How to connect

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Firecrawl to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Firecrawl once

  1. Open Connections, choose Add connection, and pick Firecrawl.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Firecrawl API key. One person generates a token in Firecrawl and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

firecrawl
Firecrawl
Apache Airflow
Apify
Boomi
Browserbase
Caspio
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Firecrawl MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Firecrawl MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Firecrawl MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Firecrawl to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Connect Firecrawl on Elaichi See pricing

Use cases

What teams do with Firecrawl through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Sales

    Research a prospect before the first call

    Ask for a prospect's homepage, pricing page, and team page to be scraped and summarized so you walk into the call knowing what they sell and who runs it.

  • Marketing

    Watch competitor pricing pages for changes

    Hand over a list of competitor pricing pages as one batch scrape and get back plan names, prices, and feature lists in a table you can compare week to week.

  • Product

    Pull structured details from many pages

    Point an extract at a set of product or listing pages and get the same fields back for each one, such as name, price, and availability, ready to drop into a spreadsheet.

  • Support

    Turn a help center into searchable text

    Crawl your own documentation site or a vendor's help center so an agent can answer customer questions from the current published pages instead of an old copy.

  • Content

    Map every page on a site before an audit

    Get a map of every link on a site in one pass, then decide which pages to scrape, rewrite, or retire.

  • Operations

    Keep an eye on Firecrawl credit spend

    Ask how many credits the team has used over the past weeks, check which crawls are still running, and stop a runaway crawl before it burns through the budget.

Try asking

  • “Which Firecrawl crawls returned errors this week?”
  • “List batch scrapes created by the Docs team.”
  • “Show browsers still running longer than an hour.”

See all 59 Firecrawl tools below

Compare

Elaichi vs Zapier MCP vs Composio for Firecrawl

All three can connect Firecrawl to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Firecrawl, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Firecrawl tools Allow or restrict single Firecrawl tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Firecrawl call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

Firecrawl tools for your AI agents

59 tools are ready to call through Elaichi's MCP endpoint the moment you connect Firecrawl, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Firecrawl gets you

6 screens from the product, each doing one job for your Firecrawl account.

The agent

Ask about crawls, get answers back.

Question your Firecrawl crawls, scrapes and browsers in plain language, answered from live records.

  • crawls
  • batch scrapes
  • browsers
  • agents

Ask Elaichi to work across your apps.

Which Firecrawl crawls returned errors this week?

List batch scrapes created by the Docs team.

Show browsers still running longer than an hour.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Firecrawl.

One governed MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

 • Connected 4 minutes ago
Cursor
M

Megan Brooks

 • Connected 2 hours ago
ChatGPT
R

Ryan Hayes

 • Connected Yesterday

Tool catalog

All 59 Firecrawl tools arrive ready.

Agents, batch scrapes, browsers and crawls exposed as tools, with no custom code.

  • Get single Firecrawl agent by ID
  • Create a Firecrawl agent
  • Delete a Firecrawl agent by ID
  • List all Firecrawl agents
ElaichiTools
Tool Action Description
Get single Firecrawl agent by ID Get Get the status of an agent job by job ID.
Create a Firecrawl agent Create Start an agent task for agentic data extraction by providing a prompt and optional URLs, schema, and model configuration.
Delete a Firecrawl agent by ID Delete Cancel an agent job by its job ID.
List all Firecrawl agents List List Firecrawl agent runs, most recent first. Returns: id, createdAt, targetHint, origin, integration, settings, status, options. Pages are fixed at 20 runs.
Get single Firecrawl batch scrape by ID Get Get the status of a batch scrape job

Toolboxes

Every team gets its own toolbox.

Curate Firecrawl crawl and browser tools per team, scoped to the work they do.

  • Engineering
  • Data
  • Docs
  • Growth
ElaichiToolboxes
Name Source template Tools Created

Engineering toolbox

Firecrawl · crawls and browsers

 Firecrawl starter 18 Mar 4, 2026

Data toolbox

Firecrawl · batch scrapes and exports

 — 9 Mar 2, 2026

Docs toolbox

Firecrawl · site crawls and page content

 — 24 Feb 27, 2026

Growth toolbox

Firecrawl · competitor page scrapes

 Firecrawl starter 6 Feb 19, 2026

Support toolbox

Firecrawl · crawl errors and reruns

 — 31 Jan 30, 2026

Research toolbox

Firecrawl · agents and extraction runs

 — 12 Jan 22, 2026

Shared connections

Teammates run crawls without seeing keys.

Each Firecrawl connection shows who connected it and which teams and members share it.

  • Engineering
  • Data Platform
  • Docs Site
  • Growth EMEA
ElaichiConnections
Connection Scope Status Access
FI

Firecrawl (Engineering)

Connected by Emily Carter

 Personal • Active 1 team · 6 members
FI

Firecrawl (Data Platform)

Connected by Jake Morgan

 Organization • Active 3 teams · 24 members
FI

Firecrawl (Docs Site)

Connected by Megan Brooks

 Organization • Active 2 teams · 11 members
FI

Firecrawl (Growth EMEA)

Connected by Tyler Reed

 Personal • Needs re-auth 1 team · 3 members
FI

Firecrawl (Support)

Connected by Ryan Hayes

 Personal • Active Not shared
FI

Firecrawl (Research)

Connected by Ashley Parker

 Personal • Active 2 teams · 9 members

Audit log

Every scrape and crawl call is recorded.

Append-only log of when, who, what happened, type and Firecrawl resource touched.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM
E

Emily Carter

emily.carter@northwind.io

 Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM
J

Jake Morgan

jake.morgan@northwind.io

 Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM
M

Megan Brooks

megan.brooks@northwind.io

 Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM
T

Tyler Reed

tyler.reed@northwind.io

 Firecrawl Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM
R

Ryan Hayes

ryan.hayes@northwind.io

 Firecrawl Crawls Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM
A

Ashley Parker

ashley.parker@northwind.io

 Firecrawl Crawls List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires, Firecrawl does the work.

Fetch crawls, group them, draft a digest, a person approves, post back.

Firecrawl digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch crawls

    Firecrawl

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s

  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve

  6. Post the digest

    Firecrawl

    Queued

Collections and dashboards

Firecrawl health, computed on a schedule.

Four metrics, 14 days of crawls created and a per team breakdown, no model involved.

Firecrawl health

Refreshed 4 minutes ago · every 15 minutes · from the crawls collection

Live

Crawls

1,284 ↓ 12%

Batch scrapes

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Crawls created

Last 14 days

By team

Share of activity

Engineering 34%

Data Platform 27%

Docs Site 21%

Growth EMEA 18%

Related connectors

More from the catalog

Browse all 600+ connectors →

FAQ

Frequently asked questions

How do I connect Firecrawl to Claude?

Connecting Firecrawl to Claude takes two steps. First, open Elaichi, choose Firecrawl, and paste in your Firecrawl API key; there is no OAuth app to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Firecrawl is ready to use in your chats.

Does Firecrawl work with ChatGPT and Cursor as well as Claude?

Yes. Once Firecrawl is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Firecrawl once and every client picks it up.

What can an AI agent actually do with Firecrawl?

With Firecrawl connected, an agent can scrape a single web page into clean text, crawl an entire site, list every link on a site, or send a batch of pages to be scraped together. It can pull structured fields such as names, prices, and dates out of pages, open a browser session to work through a page that needs clicks, and check which crawls are still running or how many credits have been used. In practice that means asking in plain language for a competitor's pricing, a prospect's company overview, or a full copy of a help center, and getting the result back in the chat.

Does connecting Firecrawl give the AI my whole Firecrawl account?

An agent working through Firecrawl can only do what the Firecrawl API key it was connected with allows, and Elaichi can narrow that further. Admins can restrict which actions are available, for example allowing scrapes and maps while blocking the ability to delete crawls or create browser sessions. Elaichi never widens what Firecrawl itself permits, and every request is written to an audit log with the name of the person who made it.

Can my team share one Firecrawl connection?

Yes. One person connects Firecrawl in Elaichi with the API key, then shares the connection with a team, and nobody else ever sees or handles that key. Each teammate still signs in to Elaichi as themselves, so the audit log shows exactly who ran each scrape, crawl, or extract through the shared Firecrawl connection.

Can I stop an agent from deleting or changing things in Firecrawl?

Yes. In Elaichi, restrictions on Firecrawl work per action, so you can block deleting crawls, batch scrapes, browser sessions, or agents while leaving scraping and crawling available. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client at all, so no prompt, however worded, can reach it.

What happens to a Firecrawl connection when someone leaves?

When someone is offboarded in Elaichi, their access to Firecrawl through the endpoint ends immediately, in every client they had set up. If Firecrawl was connected as a shared connection, it keeps working for everyone else on the team. If you want to remove Firecrawl entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other connected client at the same time.

Does the Firecrawl MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Firecrawl is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Firecrawl?

Yes. Both let Claude, ChatGPT or Cursor use Firecrawl. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Firecrawl call.

How is Elaichi different from Composio for Firecrawl?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Firecrawl: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Firecrawl in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Connect Firecrawl Talk to us
Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.