---
title: "Firecrawl MCP in Slack: ask an AI teammate to read and crawl the web | Chickpea"
description: "Use Firecrawl's MCP server from Slack. Give a channel an AI teammate connected to Firecrawl, then ask it to read a page, map a site, or search. Open source."
canonical: https://chickpea.co/connectors/firecrawl
keyword: "Firecrawl MCP in Slack"
verified: 2026-09-17
---

# A Firecrawl teammate in Slack, running on Firecrawl's MCP server.

> Chickpea gives a channel a named AI teammate that holds its own Firecrawl connection. It calls Firecrawl's MCP server at [mcp.firecrawl.dev](https://docs.firecrawl.dev/mcp-server) with an API key you create in the dashboard, so there is no client to configure. Ask it in Slack to read a page as markdown, list every URL on a site, or search for something. The answer lands in the thread.

Facts checked against the sources on September 17, 2026. The HTML page is at https://chickpea.co/connectors/firecrawl; every connector is listed at https://chickpea.co/connectors; the site index for agents is at https://chickpea.co/llms.txt.

**Firecrawl** (Firecrawl, https://www.firecrawl.dev): Search, scrape, crawl, and map websites into structured content. Category: Search and research. Lane: Vendor MCP server. Sign in: API key.

**Chickpea**: an open source Slack app that gives a workspace named AI teammates, each with its own handle, instructions, memory, connected accounts, schedules, and model, deployed to your own Cloudflare account or a Node host.

## What people ask it
The teammate in these examples is @growth, published to #growth.

### Read a page as markdown
- @growth read northwind.co/pricing and tell me what changed since the version in this thread
- @growth summarise this changelog page and say which items affect our API

One URL in, clean text back. Firecrawl documents a `markdown` output format. It also documents a main-content filter that drops headers, navigation, and footers before the markdown is generated, so the teammate reads the page rather than the furniture. A read needs no confirmation.

### Map a site, then crawl the part you want
- @growth map northwind.co and show me the docs pages that mention migrations
- @growth crawl their whole help centre and pull every claim about uptime

Mapping discovers a site's URLs and is cheap. A crawl is not. Firecrawl charges one credit a page for a basic scrape, crawl, or map, so a large site is a real bill. Ask for a whole site and the teammate comes back with the size it found and waits for a yes before it spends anything.

### Search the web
- @growth search for what people are saying about northwind pricing this month
- @growth find the three best write-ups of the new EU accessibility rules and give me the links

Firecrawl's search tool covers web, news, image, and developer sources, and search bills two credits per ten results. The teammate posts the links it used, so anyone in the channel can check where an answer came from instead of trusting the summary.

### Pull structured fields out of a page
- @growth get the plan names, seat prices, and trial lengths from northwind.co/pricing as a table
- @growth from each of these six job posts, pull the title, the location, and the salary band

Firecrawl takes a JSON schema on a scrape and returns fields that match it. The answer arrives as a table in the thread rather than as prose you have to re-read. Same one credit a page. Nothing is written anywhere until you ask for that separately.

### On a schedule
- @growth every Monday at 8am Pacific, read northwind.co/pricing and post here if anything changed
- @growth every weekday at 7am Eastern, search for mentions of us from the last day

A schedule saves on the spot. It needs an explicit time zone, runs under the Firecrawl connection of the person who asked, and is paused rather than run if that connection goes away. Keep the page count small, because every run spends credits.

### Example conversations

**Read a page**
> **Priya:** @growth read northwind.co/pricing and tell me what changed since the version in this thread.
> **@growth:** Three changes. Team went from 18 to 22 USD a seat. The 14-day trial is now 7 days. A new Scale tier sits above Business with pricing on request, and the old enterprise contact form is gone. Everything else reads the same.

**Map a site**
> **Marco:** @growth map northwind.co and show me the docs pages that mention migrations.
> **@growth:** 412 URLs on the site, 89 of them under /docs. Six mention migrations in the title or the path.
>
> | Path | Title | Depth |
> |---|---|---|
> | /docs/migrate | Migrating to v3 | 2 |
> | /docs/migrate/postgres | From Postgres | 3 |
> | /docs/migrate/csv | From a CSV export | 3 |
> | /docs/guides/downtime | Migrations without downtime | 3 |
> | /changelog/v3 | v3 and the migration path | 2 |
> | /blog/why-we-migrated | Why we migrated | 2 |

**Crawl a whole site**
> **Dana:** @growth crawl all of northwind.co and pull every claim they make about pricing.
> **@growth:** The map came back with 412 URLs. A basic crawl costs one credit a page, so all of it is about 412 credits of your Firecrawl balance. I am asking first. The 31 pages under /pricing and /compare hold almost every pricing claim, if you want the cheap version.
> Buttons: Crawl /pricing and /compare · Crawl all 412 · Leave it

**Every Monday**
> **Sofia:** @growth every Monday at 8am Pacific, read northwind.co/pricing and post here if anything changed.
> **@growth:** Saved. Mondays at 8:00 AM Pacific I’ll read that page and post the diff in #growth, or say nothing if it is unchanged. First run is Mon Sep 22. One page is one credit. It runs on your Firecrawl connection, so say "pause the pricing watch" to stop it.

## Connect Firecrawl
1. In Firecrawl, open [the dashboard's API keys page](https://www.firecrawl.dev/app/api-keys) and create a key. It starts `fc-`. Firecrawl's own advice is to keep a key in a secret store and never in the MCP URL, which is what Chickpea does with it.
2. In Chickpea Admin, open the teammate, then **Connections**, find **Firecrawl**, and choose **Connect**. Or ask in Slack, `@growth connect Firecrawl`, and follow the link it posts.
3. Choose who uses it. **Team** is one shared key that everyone who can use the teammate acts through, and one credit balance for the channel. **Personal** means each member pastes their own key and spends their own credits.
4. Paste the `fc-…` key into the write-only **Credential** field. It is stored once on your deployment and never returned to the browser. Chickpea then connects to `mcp.firecrawl.dev/v2/mcp` and records the tools the server answered with.
5. Ask something small. `@growth read example.com and tell me what it sells` is a good first question, because it is one page and one credit.

A connection belongs to one teammate. Giving a second teammate Firecrawl means a second key, so the support teammate spends its own credits and never inherits the growth teammate's balance.

## What the teammate is handed with Firecrawl
There is no built-in Chickpea skill for Firecrawl, and none is needed. The tools arrive from Firecrawl's MCP server: Chickpea connects before it saves anything, records what the server answered with, and exposes only those tools. Firecrawl documents `firecrawl_scrape` for one URL, `firecrawl_map` to discover a site's URLs, `firecrawl_search` for web, news, image, and developer sources, and `firecrawl_crawl` to traverse a site or a section, alongside others it marks as subject to your plan.

Firecrawl documents the server, its URL, and its tools: https://docs.firecrawl.dev/mcp-server

## Beside Firecrawl
- **Exa:** Exa finds the pages worth reading, Firecrawl reads them properly
- **Ahrefs:** What a competitor ranks for, next to what their page actually says
- **Google Search Console:** Your own search performance, checked against the page that earns it
- **Notion:** The research lands in a Notion page instead of scrolling out of the channel
- All 37 connectors: https://chickpea.co/connectors

## Questions people ask

### Does Firecrawl have MCP?
Yes. Firecrawl runs a hosted MCP server at mcp.firecrawl.dev/v2/mcp over streamable HTTP, authorized with your API key as a bearer token, and documents setup for editors and chat clients. Chickpea connects to that same server, so a teammate in Slack uses it without any of those clients installed.

### How do I add Firecrawl MCP to Claude Code or Cursor?
Follow Firecrawl's own docs, since each client keeps its own config file and its own way of holding the key. For Slack there is no config file. Open the teammate in Chickpea Admin, choose Firecrawl, paste the key once, and ask. Or ask "@growth connect Firecrawl" in the channel and follow the link it posts.

### Which MCP is best for web scraping?
That depends on what you are doing, and the honest answer is that this page cannot rank them. Firecrawl is the one Chickpea ships a preset for. It has a documented hosted server, tools for scraping, mapping, searching, and crawling, and credits you can watch. What Chickpea adds is the place you use it from: a Slack channel, where the page the teammate read is in the thread for everyone.

### Is Firecrawl MCP free?
Firecrawl's pricing page lists a free tier of 1,000 credits a month, refreshed monthly, with no credit card required. Paid plans start at 5,000 credits a month. Chickpea itself adds nothing to that. It is Apache 2.0, runs on your own Cloudflare account, and has no seats and no metering.

### What does a crawl cost?
Firecrawl bills in credits, shared across its endpoints. Its pricing page says one credit is one page on a basic scrape, crawl, or map. Search costs two credits per ten results, and advanced formats cost more. So a 400-page site is roughly a 400-credit crawl. That is why the teammate maps first, says the number it found, and waits for a yes. Check firecrawl.dev/pricing for the current rates.

### Does it use Firecrawl's MCP server or the API?
The MCP server. Firecrawl is a vendor MCP lane: the deployment connects to mcp.firecrawl.dev/v2/mcp over streamable HTTP and sends your key as a bearer token. Chickpea writes no Firecrawl endpoints of its own, and the connection cannot reach any other address.

### Can a page it reads tell the teammate what to do?
No. A retrieved page is task input, never permission, and the rule is enforced rather than left to the model. During a Slack turn Chickpea refuses any MCP tool whose name does not start with an unambiguous read verb unless your own message names that action. Every Firecrawl tool name begins with firecrawl_, so every call has to trace back to something a person asked for in the channel. Text on a crawled page cannot start a second crawl, and it cannot reach another connected account either.

### Where does the API key live?
On your deployment, in a write-only Credential field outside the teammate record. It never enters the model's context, the tool arguments the model writes, or Slack. The model picks a connection by id and the key goes in at the last step on the way out. Disconnect the account and the stored secret is removed, after any schedule that depended on it is paused.

### Can it crawl behind a login?
Only as far as Firecrawl itself can. Firecrawl's scrape options include a headers field, documented as headers to send with the request, usable for cookies and a user agent, so an authenticated fetch is a request that carries the right header. Chickpea holds one credential for this connector, the Firecrawl key, and none for the sites you point it at. Putting a session cookie for another service into a Slack message is a bad trade, so treat this connector as one for the public web.

### Firecrawl or Exa?
Both are connectors, and a teammate can hold both. Firecrawl calls itself the web data API to search, scrape, and interact with the web at scale. Reach for it when you know the URL and want the page as clean markdown or as fields. Exa calls itself the world's data for AI agents and searches an index of the public web. Reach for it when you do not know the URL yet. The usual pairing is Exa to find and Firecrawl to read.

## Sources
- [Chickpea docs: connector catalog, the Firecrawl preset, its lane and its bearer key](https://docs.chickpea.co/reference/connector-catalog/)
- [Chickpea docs: connections, team and personal accounts, the binding as a ceiling](https://docs.chickpea.co/agents/connections/)
- [Chickpea docs: authority and confirmation, including the read-verb gate on MCP tools](https://docs.chickpea.co/security/authority-and-confirmation/)
- [Chickpea docs: connect a service, the write-only credential field and the Slack link](https://docs.chickpea.co/agents/connect-a-service/)
- [Chickpea docs: schedules, time zones and what a paused schedule does](https://docs.chickpea.co/agents/schedules/)
- [Chickpea source: the Firecrawl preset (server URL, transport, bearer key)](https://github.com/pejmanjohn/chickpea/blob/main/src/config/presets.ts)
- [Chickpea source: an MCP connection exposes approved tools that are still discovered](https://github.com/pejmanjohn/chickpea/blob/main/src/config/types.ts)
- [Firecrawl docs: the MCP server, its URL, the bearer key, and where to keep it](https://docs.firecrawl.dev/mcp-server)
- [Firecrawl docs: the MCP tools, including scrape, map, search, and crawl](https://docs.firecrawl.dev/mcp-server/tools)
- [Firecrawl docs: the scrape request, its formats, its JSON schema, and its headers field](https://docs.firecrawl.dev/api-reference/endpoint/scrape)
- [Firecrawl: pricing, the free tier, and what a credit buys](https://www.firecrawl.dev/pricing)
- [Exa: how Exa describes what it indexes and searches](https://exa.ai)
- [Chickpea source on GitHub](https://github.com/pejmanjohn/chickpea)

## More
- [Ahrefs MCP in Slack](https://chickpea.co/connectors/ahrefs.md)
- [Airtable MCP in Slack](https://chickpea.co/connectors/airtable.md)
- [Asana AI agent in Slack](https://chickpea.co/connectors/asana.md)
- [Jira and Confluence MCP in Slack](https://chickpea.co/connectors/atlassian.md)
- [BugSnag MCP in Slack](https://chickpea.co/connectors/bugsnag.md)
- [Cloudflare MCP in Slack](https://chickpea.co/connectors/cloudflare-api.md)
- [Exa MCP in Slack](https://chickpea.co/connectors/exa.md)
- [Fireflies MCP in Slack](https://chickpea.co/connectors/fireflies.md)
- [Gamma MCP in Slack](https://chickpea.co/connectors/gamma.md)
- [Gmail AI agent in Slack](https://chickpea.co/connectors/gmail.md)
- [Gong AI agent in Slack](https://chickpea.co/connectors/gong-managed.md)
- [Google Ads AI agent in Slack](https://chickpea.co/connectors/google-ads.md)
- [Google Analytics AI agent in Slack](https://chickpea.co/connectors/google-analytics.md)
- [Google Calendar AI agent in Slack](https://chickpea.co/connectors/google-calendar.md)
- [Google Docs AI agent in Slack](https://chickpea.co/connectors/google-docs.md)
- [Google Drive AI agent in Slack](https://chickpea.co/connectors/google-drive.md)
- [Google Search Console AI agent in Slack](https://chickpea.co/connectors/google-search-console.md)
- [Google Sheets AI agent in Slack](https://chickpea.co/connectors/google-sheets.md)
- [Google Slides AI agent in Slack](https://chickpea.co/connectors/google-slides.md)
- [Granola MCP in Slack](https://chickpea.co/connectors/granola.md)
- [HubSpot AI agent in Slack](https://chickpea.co/connectors/hubspot-managed.md)
- [Hugging Face MCP in Slack](https://chickpea.co/connectors/huggingface.md)
- [incident.io MCP in Slack](https://chickpea.co/connectors/incident-io.md)
- [Intercom MCP in Slack](https://chickpea.co/connectors/intercom.md)
- [Linear MCP in Slack](https://chickpea.co/connectors/linear.md)
- [LunarCrush MCP in Slack](https://chickpea.co/connectors/lunarcrush.md)
- [Meta Ads MCP in Slack](https://chickpea.co/connectors/meta-ads.md)
- [Monday.com MCP in Slack](https://chickpea.co/connectors/monday.md)
- [Neon MCP in Slack](https://chickpea.co/connectors/neon.md)
- [Notion Slack integration with an AI agent](https://chickpea.co/connectors/notion-managed.md)
- [PostHog MCP in Slack](https://chickpea.co/connectors/posthog.md)
- [Sentry MCP in Slack](https://chickpea.co/connectors/sentry.md)
- [Stripe MCP in Slack](https://chickpea.co/connectors/stripe.md)
- [Supabase MCP in Slack](https://chickpea.co/connectors/supabase.md)
- [YouTube AI agent in Slack](https://chickpea.co/connectors/youtube-managed.md)
- [Zendesk AI agent in Slack](https://chickpea.co/connectors/zendesk.md)
- [All connectors](https://chickpea.co/connectors.md)

## Try Chickpea
- Site: https://chickpea.co/
- Deploy to Cloudflare: https://deploy.workers.cloudflare.com/?url=https://github.com/pejmanjohn/chickpea
- Source, Apache 2.0: https://github.com/pejmanjohn/chickpea
- Docs: https://docs.chickpea.co