MCP Gateway · Claude
Connect Fireflies to Claude
Sales, customer success and recruiting teams spend much of the day on calls that Fireflies records. In Claude, they can ask about those meetings in plain language: what a customer objected to, what was promised, who needs a follow-up. An Owner adds the gateway once, each person connects from Customize > Connectors, and nobody holds a Fireflies credential.
- Category
- Communication
- Tools
- 19
- Authentication
- OAuth
- Claude
- Web, desktop and mobile
Behind the MCP Gateway
Run Fireflies MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Fireflies call inspected and logged.
Set up
Add Fireflies to Claude in 4 steps
- 01
Add Fireflies from the catalog
An admin finds Fireflies in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
Fireflies uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use Fireflies
Give teams the
mcp:connectscope on the Fireflies server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Fireflies to their gateway on the next call, and removing it takes it away. - 03
Connect Claude
Add the gateway URL as a custom connector, then connect it from Customize > Connectors.
On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.
Each person opens Customize > Connectors and clicks Connect to sign in.
On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.
- 04
Sign in and use Fireflies from Claude
The first time Claude connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Fireflies needs its own OAuth grant, so each person connects it once. Until they do, Fireflies calls fail while the rest of the gateway keeps working.
From then on, Fireflies's tools appear in Claude, limited to what the person's access allows, and every call lands in the gateway's tool logs.
No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.
Use cases
What Claude users do with Fireflies
Draft a follow-up email
Ask Claude for the summary and action items from your last call with a customer, then have it draft the follow-up email that confirms next steps.
Prepare for a renewal call
Claude finds the quarter's meetings with a customer's contacts by email, reads their summaries, and lists open issues and commitments before the renewal.
Hand a recording to a colleague
Ask Claude to share a meeting transcript with a new account owner, optionally with an expiry, and revoke that access once the handoff is done.
Tools
19 tools
Each Fireflies tool can be allowed or denied per team and role at the MCP Gateway before Claude sees it.
fireflies_get_transcript
Fetches detailed meeting transcript by ID, with optional field filtering. Returns transcript content (sentences, speakers) and metadata, but excludes summary data. If you need summary data, use fireflies_get_summary instead.
fireflies_get_summary
Fetches meeting summary by ID, with optional field filtering. Returns summary data (keywords, action items, overview, etc.) and basic metadata, but excludes transcript content. If you need transcript content, use fireflies_get_transcript instead.
fireflies_get_transcripts
Queries multiple meeting transcripts using filter properties (date, keyword, email, etc.). Returns basic metadata and transcript summary. Does NOT accept transcriptId as input - use fireflies_get_transcript() multiple times to get detailed transcript content.
fireflies_get_active_meetings
Retrieves a list of currently active (in-progress) meetings from Fireflies.ai. 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_user
Fetches user account details. Returns profile info, transcript counts, meeting activity, and admin status. If no user ID provided, returns current authenticated user data.
fireflies_get_usergroups
Fetches user groups for the authenticated user or their team. Returns group details including name, handle, and members. Use mine=true to get only groups the user belongs to, or mine=false (default) to get all groups in the team.
Control
What Speakeasy can see and stop in Claude
The gateway covers every client the same way. The rest depends on what Claude exposes to Speakeasy.
Tool logs
Gateway
Every Fireflies call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Fireflies tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Fireflies can reject a tool request before it reaches the server, or withhold a result from Claude. MCP-scoped policies are enabled per organization.
Anthropic inference hooks
Claude
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Conversation import
Claude
Claude conversations can be imported through Anthropic's Compliance API for review after the fact.
- Custom connectors need a Claude plan that supports them.
- Budgets don't cover Claude web and desktop usage.
Questions
Frequently asked questions
Can Claude Enterprise block a prompt about a meeting?
Can Claude conversations about meetings be reviewed later?
How do Claude users get Fireflies?
Are Fireflies calls from Claude logged?
Connect more