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.
-
How it connects. Connects over OAuth. 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.
19 tools
How to connect
How to connect Fireflies.ai to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Fireflies.ai once
-
Open Connections, choose Add connection, and pick Fireflies.ai.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Fireflies.ai. Fireflies.ai's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
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.
Fireflies.ai 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.
Fireflies.ai 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 today. The plugin directory lives at chatgpt.com/plugins.
Fireflies.ai 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.
Connect Fireflies.ai 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.
Use cases
What teams do with Fireflies.ai through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Pull the commitments out of a discovery call
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.
-
Customer success
Brief yourself before a renewal conversation
Search every recorded meeting with an account and read the summaries side by side. Walk in knowing what was promised last quarter.
-
Support
Find where a customer first described the bug
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.
-
Product
Turn a week of customer calls into themes
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.
-
Leadership
See how much time goes to meetings
Ask for meeting analytics by person or group, see which meetings are running right now, and check whether recordings landed in the right channel.
-
Recruiting
Keep interview recordings in the right hands
Rename interview meetings consistently, move them into the hiring channel, and revoke access when a panel member rolls off.
Try asking
- “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.”
Compare
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.
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, 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
Fireflies.ai tools for your AI agents
19 tools are ready to call through Elaichi's MCP endpoint the moment you connect Fireflies.ai, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Fireflies.ai builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Fireflies.ai gets you
6 screens from the product, each doing one job for your Fireflies.ai account.
The agent
Ask about any recorded meeting in plain language.
Summaries, transcripts and soundbites from Fireflies.ai, answered from live meetings.
- meetings
- transcripts
- soundbites
- channels
Ask Elaichi to work across your apps.
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.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint brings Fireflies.ai into every client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
19 Fireflies.ai tools, ready without writing code.
Transcripts, summaries, soundbites, channels, analytics and sharing, covered out of the box.
- Fireflies search
- Fireflies get transcripts
- Fireflies get transcript
- Fireflies fetch
ElaichiToolsToolboxes
Every team gets its own Fireflies.ai toolbox.
Sales reads call summaries, product pulls research transcripts, each from a toolbox scoped to them.
- Sales
- Customer success
- Support
- Product
ElaichiToolboxesShared connections
Share a Fireflies.ai connection, never a password.
Teammates search meetings through one connection and never see the credential behind it.
- Sales EMEA
- Customer success
- Support
- Product research
ElaichiConnectionsAudit log
Every transcript read is on the record.
When, who, what happened and which Fireflies.ai meeting, in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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
Friday's call recap drafts itself and gets approved.
A schedule fetches Fireflies.ai transcripts, groups them, drafts a digest, and posts after one approval.
Fireflies.ai digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch meetings
Fireflies.ai
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 Michael Brennan
Approve Deny -
Post the digest
Fireflies.ai
Queued
Collections and dashboards
Meeting health, computed on a schedule, no asking.
Meetings recorded over 14 days, by team, pulled from Fireflies.ai with no model involved.
Fireflies.ai health
Refreshed 4 minutes ago · every 15 minutes · from the meetings collection
Meetings
1,284 ↓ 12%
Transcripts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Meetings created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Customer success 27%
Support 21%
Product research 18%
Related connectors
More from the catalog
FAQ
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 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.
Put Fireflies.ai in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
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.