Skip to main content
Back to the Fireflies MCP server

MCP Gateway · Claude Code

Fireflies icon

Connect Fireflies to Claude Code

Decisions about code often get made on calls and then lost. With Fireflies connected, Claude Code can search past meeting transcripts for what the team agreed before it writes code that contradicts it. Agent hooks send each tool call to Speakeasy for an allow or deny decision, and the OpenTelemetry exporter ties each session to the developer running it.

Category
Communication
Tools
19
Authentication
OAuth
Claude Code
CLI

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.

Deploy on MCP Gateway

Set up

Add Fireflies to Claude Code in 4 steps

  1. 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.

  2. 02

    Choose who can use Fireflies

    Give teams the mcp:connect scope 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.

  3. 03

    Connect Claude Code

    Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.

    Run the command below with your organization gateway URL.

    Open /mcp in Claude Code and choose Authenticate to sign in.

    claude mcp add --transport http --scope user \
      'speakeasy' \
      'https://<organization host>/mcp/gateway/<organization slug>'
  4. 04

    Sign in and use Fireflies from Claude Code

    The first time Claude Code 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 Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.

To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.

Use cases

What Claude Code users do with Fireflies

Check what an architecture review decided

Before refactoring a service, ask Claude Code to find the review where it was discussed and pull the agreed approach and any objections from the transcript.

fireflies_searchfireflies_get_transcript

Turn standup action items into TODOs

Claude Code reads the summary of this morning's standup, picks out the action items that belong to you, and adds them as a checklist in the branch.

fireflies_get_summary

Quote a customer's bug report

When a bug came up on a customer call, Claude Code fetches the full transcript and copies the exact steps the customer described into a reproduction test.

fireflies_fetch

Tools

19 tools

Each Fireflies tool can be allowed or denied per team and role at the MCP Gateway before Claude Code 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.

See all 19 tools

Control

What Speakeasy can see and stop in Claude Code

The gateway covers every client the same way. The rest depends on what Claude Code 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 Code. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Claude Code

Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.

User attribution

Claude Code

Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.

Budgets

Claude Code

Spend limits can block Claude Code traffic once a budget is reached.

Device agent and MDM

Claude Code

The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.

Anthropic inference hooks

Claude Code

On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).

  • Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
  • Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.

Questions

Frequently asked questions

Can Claude Code share or move meeting recordings?
Only if the role allows it. fireflies_share_meeting, fireflies_revoke_meeting_access and fireflies_move_meeting change who can see a meeting or where it's filed, and the gateway decides which Fireflies tools each team can call.
Is Claude Code's Fireflies activity tied to a person?
Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.
How do Claude Code users get Fireflies?
An admin adds Fireflies from the Speakeasy MCP Catalog and grants access by team or role. Add the organization gateway as an HTTP MCP server, then authenticate from /mcp. Each person then sees only the Fireflies tools their access allows.
Are Fireflies calls from Claude Code logged?
Yes. Fireflies calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Fireflies in other clients

AI everywhere.

Control here.