# Fireflies.ai MCP connector

The Fireflies.ai connector brings meeting transcripts, summaries, soundbites and channels into Elaichi, so Claude, ChatGPT, Cursor or the Elaichi Agent can search and work with recorded meetings as the person who signed in.

Source: https://elaichi.ai/connectors/fireflies-ai/

## Facts

| | |
| --- | --- |
| Application | Fireflies.ai |
| Category | Conversational Intelligence |
| AI tools | 19 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Fireflies.ai builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | support@fireflies.ai |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Fireflies.ai is connected

- Summarize yesterday's call with Acme and list every commitment we made.
- Find the meeting where the customer mentioned the pricing page bug.
- Clip a soundbite of the CFO explaining the budget timeline.

## Connect Fireflies.ai in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Fireflies.ai.
2. Optionally set Share with, then press Connect.
3. Approve it in Fireflies.ai. Fireflies.ai's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Fireflies.ai tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Fireflies.ai MCP connector for Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

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

## Fireflies.ai MCP connector for ChatGPT

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

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

## Fireflies.ai MCP connector for Cursor

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

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

## Connect Fireflies.ai to any MCP client

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

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

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Fireflies.ai tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Fireflies.ai through Elaichi

### Pull the commitments out of a discovery call

Sales. After a call ends, ask for the summary and the exact lines where the prospect named a budget or a timeline. Clip the key moment as a soundbite for the deal review.

### Brief yourself before a renewal conversation

Customer success. Search every recorded meeting with an account and read the summaries side by side. Walk in knowing what was promised last quarter.

### Find where a customer first described the bug

Support. Search transcripts for the error or feature a customer mentioned and read the exact exchange. Share that meeting with the engineer who picks up the ticket.

### Turn a week of customer calls into themes

Product. Pull transcripts from the research channel and have the agent group what customers asked for. Create soundbites so the team hears it in the customer's own words.

### See how much time goes to meetings

Leadership. Ask for meeting analytics by person or group, see which meetings are running right now, and check whether recordings landed in the right channel.

### Keep interview recordings in the right hands

Recruiting. Rename interview meetings consistently, move them into the hiring channel, and revoke access when a panel member rolls off.

## Elaichi vs Zapier MCP vs Composio for Fireflies.ai

All three can connect Fireflies.ai 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. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Fireflies.ai tools | Allow or restrict single Fireflies.ai 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 Fireflies.ai 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Fireflies.ai to Claude?

Connect Fireflies.ai in Elaichi first: pick it from the catalog and sign in to your Fireflies.ai account in the window that opens, the same way you log in on the web. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks, and your Fireflies.ai meetings are available.

### Does Fireflies.ai work with ChatGPT and Cursor as well as Claude?

Yes. Once Fireflies.ai 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 Fireflies.ai once and every client you use picks it up.

### What can an AI agent actually do with my Fireflies.ai data?

It can search your Fireflies.ai meetings, read a transcript or its summary, pull the soundbites from a call, and tell you which meetings are happening right now. It can also rename a meeting, move it into a channel, share it with a colleague or take that access back, and report meeting analytics for a person or group. Short, concrete asks work best, such as the summary of yesterday's call with Acme, rather than a long paragraph of instructions.

### Does connecting Fireflies.ai give the AI every meeting in my workspace?

No. The AI sees only the Fireflies.ai meetings, channels and transcripts that the person who signed in can already see, because every request runs as that person. Elaichi can narrow that further with restrictions, and it can never widen it beyond what Fireflies.ai itself allows that person.

### Can my team share one Fireflies.ai connection?

Yes. One person connects Fireflies.ai in Elaichi and shares it with a team, and nobody else ever handles a credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who read a transcript or shared a meeting.

### Can I stop an agent from sharing or changing meetings in Fireflies.ai?

Yes. Restrictions in Elaichi work per action, so you can allow searching and reading Fireflies.ai transcripts while blocking sharing, renaming, moving or revoking access to meetings. A restricted action is never advertised to the AI client at all, so no prompt, however worded, can reach it.

### What happens to a Fireflies.ai connection when someone leaves?

Offboarding that person in Elaichi ends their access to Fireflies.ai through every client at once. If they had shared a Fireflies.ai connection with a team, it keeps working for everyone else. Disconnecting Fireflies.ai once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.

### Does the Fireflies.ai MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Fireflies.ai 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 Fireflies.ai?

Yes. Both let Claude, ChatGPT or Cursor use Fireflies.ai. 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 Fireflies.ai call.

### How is Elaichi different from Composio for Fireflies.ai?

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 Fireflies.ai: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 19 Fireflies.ai tools

Every tool below is callable through https://api.elaichi.ai/mcp once Fireflies.ai is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Fireflies search** (Search). Advanced search for meeting transcripts using mini grammar syntax. (Experimental)
- **Fireflies get transcripts** (Get). Query multiple meetings with structured filters. Returns metadata and summaries.
- **Fireflies get transcript** (Get). Fetch detailed transcript by ID with sentences, speakers, and timestamps. Excludes summary data. If the meeting is currently live (is_live: true), returns a point-in-time snapshot of the live transcript with sentences captured so far.
- **Fireflies fetch** (Action). Retrieve complete meeting data including transcript, summary, and metadata. (Experimental)
- **Fireflies get summary** (Get). Fetch meeting summary by ID with action items, keywords, and overview. Excludes transcript content.
- **Fireflies get active meetings** (Get). Retrieves a list of currently active (in-progress) meetings. Returns meeting details including ID, title, organizer, meeting link, start/end time, privacy, and state. Admins can query active meetings for any user; regular users can only query their own.
- **Fireflies get analytics** (Get). Retrieves team and per-user meeting and conversation analytics. Returns meeting counts, durations, conversation metrics (filler words, questions, monologues, sentiment, talk-listen ratio, words per minute), and comparison data against previous periods. Team-level analytics…
- **Fireflies share meeting** (Share). Shares a meeting transcript with specified email addresses. The authenticated user must be the owner of the meeting or a team admin. Up to 100 emails can be provided. Optionally set an expiry period for the shared access.
- **Fireflies revoke meeting access** (Revoke). Revokes a previously shared meeting access for a specific email address. The authenticated user must be the owner of the meeting or a team admin.
- **Fireflies update meeting title** (Update). Updates the title of a meeting transcript. The authenticated user must be the owner of the meeting or a team admin. The title must be between 5 and 256 characters.
- **Fireflies move meeting** (Move). Moves one or more meeting transcripts to a specified channel/folder. The authenticated user must be the owner of the meetings or a team admin. Up to 5 meeting IDs can be provided.
- **Fireflies list channels** (List). Lists all channels/folders available to the authenticated user. Returns channel details including ID, title, privacy setting, and members.
- **Fireflies get channel** (Get). Retrieves details of a specific channel/folder by its ID. Returns channel title, privacy setting, and member list.
- **Fireflies get soundbites** (Get). Fetches soundbites (short shareable audio/transcript clips from meetings). Can filter by transcript, ownership, or team. At least one of mine, transcript_id, or my_team must be provided.
- **Fireflies create soundbite** (Create). Creates a soundbite (clip) from a meeting transcript. A soundbite is a short audio/video segment extracted from a meeting. The authenticated user must have write access to the meeting.
- **Fireflies get user** (Get). Fetch user account details. Returns authenticated user if no ID provided.
- **Fireflies get usergroups** (Get). Fetch user groups for the authenticated user or team.
- **Fireflies get user contacts** (Get). Fetch contact list sorted by most recent meeting date.
- **Fireflies get rule executions** (Get). Retrieves rule execution logs grouped by meeting. Shows which automation rules were triggered on meetings, including the actions taken (sharing, moving to channels, changing privacy). Requires Enterprise tier access. Results are paginated.