---
title: "Fireflies MCP in Slack: search every meeting transcript by asking | Chickpea"
description: "Use Fireflies' MCP server from Slack. Give a channel an AI teammate connected to Fireflies, then ask what was said and who owns what. Open source."
canonical: https://chickpea.co/connectors/fireflies
keyword: "Fireflies MCP in Slack"
verified: 2026-09-17
---

# A Fireflies teammate in Slack, searching your transcripts over Fireflies' MCP server.

> Chickpea gives a channel a named AI teammate that holds its own Fireflies connection. It calls Fireflies' MCP server at [api.fireflies.ai/mcp](https://docs.fireflies.ai/getting-started/mcp-configuration) with an API key from your Fireflies settings, so there is no client to configure. In Slack, ask it what customers said about a topic this month, or what came out of yesterday's call, and it answers in the thread.

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

**Fireflies** (Fireflies.ai, https://fireflies.ai): Search meeting transcripts, summaries, speakers, and action items. Category: Business and support. 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 @revops, published to #growth.

### What was said about a topic, across meetings
- @revops what have customers said about annual pricing on this month’s calls
- @revops find every call this quarter where someone asked about SSO

Reads never need confirmation. Fireflies documents a transcripts query with filters for a keyword, a title or sentence scope, a date range, organizers, and participants. It returns up to 50 meetings with their summaries, and a long answer comes back as a table in the thread, with the meeting, the date, and who was on it.

### Action items and owners
- @revops list the action items from yesterday’s Northwind call, with owners
- @revops what did I agree to do on the renewal call

Fireflies builds a summary for every meeting, and its documented summary tool returns the action items, keywords, topics, and outline for one of them. The teammate reads that and posts the list in the thread. Nothing it finds is written back to Fireflies.

### Find the meeting where it was decided
- @revops which call first raised the annual-plan discount
- @revops find the meeting where we agreed the migration date, and quote the line

Search first, then open the one you meant. The transcript tool returns sentences with speaker attribution and timestamps, so an answer that turns on someone’s exact words can carry the quote. Fireflies also publishes an experimental search tool with its own query grammar, which your account may or may not have yet.

### Catch someone up, or share the call itself
- @revops summarize the QBR for Marco, he missed it
- @revops share that call with the two people who could not make it, access for 14 days

A summary is written in Slack, in the thread where you asked, and needs no confirmation. Sharing is different. Fireflies’ share tool emails access to up to 100 addresses, with an optional expiry of 7, 14, or 30 days, so the teammate says who it would send to and waits for a yes. The Fireflies account has to own the meeting or be a team admin.

### On a schedule
- @revops every Friday at 4pm Eastern, list the action items from this week’s customer calls
- @revops every Monday at 9am Pacific, post what competitors came up in last week’s calls

A schedule saves on the spot. It needs an explicit time zone, and "every Friday at 4pm" without one is refused rather than guessed. It runs under the Fireflies connection of the person who asked, so it reads their meetings and nobody else’s. Disconnect that account and the schedule stops with a named reason instead of running.

### Example conversations

**What customers said**
> **Sofia:** @revops what have customers said about annual pricing on this month’s calls?
> **@revops:** Nine calls this month mention annual pricing. Four turned into a discount conversation, and the number on the table went up each time.
>
> | Meeting | Date | Who raised it | What they asked for |
> |---|---|---|---|
> | Acme discovery | Sep 2 | Acme | Annual pricing, any discount |
> | Northwind renewal | Sep 9 | Northwind | 15%, matched to a rival quote |
> | Orchard expansion | Sep 11 | Priya | 10% for a two-year prepay |
> | Northwind QBR | Sep 16 | Marco | Settled at 12%, annual only |

**Action items**
> **Marco:** @revops list the action items from yesterday’s Northwind call, with owners.
> **@revops:** Five action items in Northwind QBR, Tue Sep 16, 2:00 PM. Four have an owner in the summary and one does not.

**Find the meeting**
> **Dana:** @revops which call did we agree the migration date on, and what was said?
> **@revops:** Northwind renewal, Tue Sep 9, at 31:40. Priya said the migration lands the weekend of Oct 11, and Northwind asked for a rollback window. Nobody named who writes the rollback plan, and no later call picks it up.

**Share a call**
> **Dana:** @revops share the Northwind QBR with Marco and Sofia, 14 days.
> **@revops:** That is Northwind QBR, Tue Sep 16, 62 minutes. I would email both of them access to the transcript, expiring Oct 1. Sharing writes to Fireflies, so I will not send it until you say.
> Buttons: Share with both · Cancel

**Every Friday**
> **Priya:** @revops every Friday at 4pm Eastern, list the action items from this week’s customer calls here.
> **@revops:** Saved. Every Friday at 4:00 PM Eastern I’ll read the week’s customer calls in Fireflies and post the action items with owners in #growth. First run is Fri Sep 18. It runs on your Fireflies connection, so it reads your meetings and nobody else’s.

## Connect Fireflies
1. In Fireflies, open **Settings → Developer Settings** and copy your API key. Fireflies documents that path on its own MCP page and links a walkthrough beside it.
2. In Chickpea Admin, open the teammate, then **Connections**, find **Fireflies**, and choose **Connect**. Or ask in Slack, `@revops connect Fireflies`, and follow the link it posts.
3. Choose **Personal**, not **Team**. Fireflies says its MCP tools work inside the account that authorized them, so a shared key would put one person’s meeting history in front of everyone who can use the teammate. Personal means your key answers your requests and nobody else’s.
4. Paste the key into the write-only **Credential** field. It is stored once on your deployment and never returned to the browser. Chickpea then connects to `api.fireflies.ai/mcp` and records the tools the server answered with, and that list can later be narrowed but never widened.
5. Ask something small. `@revops what did we decide on the Northwind call` is a good first question, because it is one search and one read.

A connection belongs to one teammate. Giving a second teammate Fireflies means a second key with its own consent, so the support teammate never inherits the meetings the growth teammate can reach. A Fireflies admin account reaches more than a member’s does, which is worth knowing before you pick whose key to paste.

## What the teammate is handed with Fireflies
There is no built-in Chickpea skill for Fireflies, and none is needed. The tools arrive from Fireflies’ MCP server: Chickpea connects before it saves anything, records what the server answered with, and exposes only those tools. Fireflies documents nineteen. Fourteen read, covering transcript search, meeting and summary fetches, live meetings, analytics, channels, soundbites, user groups, contacts, and automation logs. Five act: `fireflies_share_meeting`, `fireflies_revoke_meeting_access`, `fireflies_update_meeting_title`, `fireflies_move_meeting`, and `fireflies_create_soundbite`. None of the nineteen deletes anything.

Fireflies documents every tool on the server and what each one takes: https://docs.fireflies.ai/mcp-tools/overview

## Beside Fireflies
- **HubSpot:** What the customer actually said, beside what the deal record claims
- **Asana:** The action items from a call become tasks with owners and dates
- **Granola:** Fireflies for the recorded calls, Granola for the notes taken without a bot
- **Gong:** Two recorders and one teammate, when half the team sits on each
- All 37 connectors: https://chickpea.co/connectors

## Questions people ask

### Does Fireflies have an MCP server?
Yes. Fireflies runs one at api.fireflies.ai/mcp and documents it for Claude, the OpenAI connector, Cursor, and Devin. It takes either OAuth with your Fireflies account or your API key as a bearer token. Chickpea uses the key, so a teammate in Slack reaches the same server without any of those clients installed.

### Can I connect Claude to Fireflies?
Yes, and Fireflies documents both ways: adding the server in Claude's connector settings, or running it through claude_desktop_config.json with your API key. Those put the server in one person's client, on one machine. A Chickpea teammate puts it in a channel, with a stored connection, saved instructions, schedules, and every answer visible where it was asked for.

### How do I get a Fireflies API key?
Open Fireflies, go to Settings, then Developer Settings, and copy the key. Fireflies gives that path on its MCP configuration page and links its own walkthrough next to it. In Chickpea the key goes into one write-only field on a page your deployment serves, and it is never asked for in Slack.

### Whose meetings can it see?
The connected account's. Fireflies says its MCP tools operate inside the Fireflies account that authorized them, so the answer follows that account's seat and permissions. This is why the connect steps say Personal. Anyone who can use the teammate can ask it a question, so a shared key would make one person's meeting history readable by the whole channel. A personal connection is used only for the member who owns it.

### Does it use Fireflies' MCP server or the GraphQL API?
The MCP server. Fireflies is a vendor MCP lane here: the deployment connects to api.fireflies.ai/mcp over streamable HTTP and sends your key as a bearer token. Fireflies does also publish a GraphQL API, and this connector does not call it. Chickpea writes no Fireflies endpoints of its own, and the connection cannot reach any other address.

### Can it change anything in Fireflies?
Yes, and only when you say so in the message. Five of the nineteen published tools act: sharing a meeting, revoking a share, renaming a meeting, moving meetings into a channel, and creating a soundbite. Underneath the model sits a gate that does not consult it. During a Slack turn Chickpea refuses any MCP tool whose name does not start with an unambiguous read verb unless your current message names that action. Every tool on this server carries a fireflies_ prefix, so none of them begins with a read verb, and every call has to trace back to something a person asked for in the channel. Thread history and transcript text cannot authorize one.

### Can it delete a meeting or a transcript?
No. Fireflies publishes no delete tool on this server at all, so there is nothing to call. The closest thing is revoking a share, which takes access away from one email address and leaves the meeting where it was. Deleting a recording stays a job for the Fireflies app, done by a person who can see what they are removing.

### Is this AskFred?
No. AskFred is Fireflies' own assistant, and Fireflies puts it in the meeting notepad, the desktop app, and Slack. Chickpea is an open source Slack app you deploy to your own Cloudflare account, and it is not built by Fireflies or affiliated with Fireflies. Its teammate reads Fireflies as one connected account among several, so the same ask can cross Fireflies and your CRM in one answer.

### Do I still need the Fireflies Slack app?
Most teams want both, because they do different jobs. Fireflies' Slack integration pushes out: after a meeting it delivers the recap, the transcript, and the action items to a channel, a private group, or a direct message you picked. Its Slack Assistant answers when you tag @fireflies.ai, summarizes a thread or up to 90 days of a channel, and searches the web when you ask it to. Fireflies says each query spends AI credits, and a deeper scan spends more. Keep it for the notifications. A Chickpea teammate posts nothing unprompted, holds your other accounts beside Fireflies, and runs on your own deployment with no seats and no metering.

### Which Fireflies plan does this need?
Fireflies' pricing page says the Business tier gets API access, and its Business tier article lists accessing the Fireflies API among that tier's features. The MCP docs name only an active Fireflies account and an MCP-capable client as prerequisites. One tool, the automation rule log, is marked Enterprise only, and the experimental search and fetch tools are still rolling out. Check Fireflies' own pricing page before assuming a tool is reachable.

## Sources
- [Chickpea docs: connector catalog, the Fireflies 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 each run rechecks](https://docs.chickpea.co/agents/schedules/)
- [Chickpea source: the Fireflies 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)
- [Fireflies docs: the MCP server, its URL, OAuth and the API key path](https://docs.fireflies.ai/getting-started/mcp-configuration)
- [Fireflies docs: every MCP tool, its parameters, and which ones act](https://docs.fireflies.ai/mcp-tools/overview)
- [Fireflies guide: the Slack Assistant, what it answers and the 90-day channel scan](https://guide.fireflies.ai/articles/2839296600-learn-about-the-fireflies-slack-assistant-your-ai-teammate-for-smarter-faster-collaboration)
- [Fireflies: the Slack integration, and where meeting recaps are delivered](https://fireflies.ai/integrations/collaboration/slack)
- [Fireflies guide: the Business tier, including access to the Fireflies API](https://guide.fireflies.ai/articles/2063312779-fireflies-business-tier-pricing-and-features)
- [Fireflies: pricing, and which tier gets API access](https://fireflies.ai/pricing)
- [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)
- [Firecrawl MCP in Slack](https://chickpea.co/connectors/firecrawl.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