Firecrawl MCP connector
The Firecrawl connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, 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.
- Connects with an API key
- Free 14-day trial
- No credit card
Claude
Elaichi connected
Which Firecrawl crawls returned errors this week?
Working in Firecrawl with Elaichi
-
Get single Firecrawl agent by ID
-
-
Governance
/
Audit log
Last 24 hours
Claude · 9:41 AM
Done
Claude · 9:41 AM
Done
Claude · 9:41 AM
Done
ChatGPT · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect Firecrawl to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Firecrawl MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Firecrawl MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Firecrawl MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Firecrawl MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Firecrawl to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
What teams do with Firecrawl through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Firecrawl is logged.
-
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.”
What connecting Firecrawl gets you
6 screens from Elaichi, each doing one job for your Firecrawl account.
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, Cursor or Microsoft Copilot
The agent
Ask about crawls, get answers back.
Question your Firecrawl crawls, scrapes and browsers in plain language, answered from live records.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Firecrawl.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiToolsTool catalog
All 59 Firecrawl tools arrive ready.
Agents, batch scrapes, browsers and crawls exposed as tools, with no custom code.
ElaichiToolboxesToolboxes
Every team gets its own toolbox.
Curate Firecrawl crawl and browser tools per team, scoped to the work they do.
ElaichiConnectionsShared connections
Teammates run crawls without seeing keys.
Each Firecrawl connection shows who connected it and which teams and members share it.
ElaichiAudit logAudit log
Every scrape and crawl call is recorded.
Append-only log of when, who, what happened, type and Firecrawl resource touched.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Firecrawl digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch crawls
Firecrawl
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Firecrawl
Queued
Automations
A schedule fires, Firecrawl does the work.
Fetch crawls, group them, draft a digest, a person approves, post back.
Firecrawl health
Refreshed 4 minutes ago · every 15 minutes · from the crawls collection
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%
Collections and dashboards
Firecrawl health, computed on a schedule.
Four metrics, 14 days of crawls created and a per team breakdown, no model involved.
For IT and engineering
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.
| 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 | Free for one person; $15 per user per month on Gold. | 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.
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.
No tools match your search.
Questions, answered
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, Microsoft Copilot, 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 restricting 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 I stop an agent from deleting or changing things in Firecrawl?
Yes. In Elaichi, restrictions on Firecrawl work per action, so you can restrict deleting crawls, batch scrapes, browser sessions, or agents while leaving scraping and crawling available. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot, 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, Microsoft Copilot, 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 of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
- ChatGPT
- Claude
- Cursor
- Microsoft Copilot