Skip to main content
Back to the Fireflies MCP server

MCP Gateway · Cursor

Fireflies icon

Connect Fireflies to Cursor

Product and design calls often settle details the ticket never captured. With Fireflies in Cursor, you can pull the relevant part of a meeting into the editor's chat while you build the feature. Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and every hook event carries the user's email.

Category
Communication
Tools
19
Authentication
OAuth
Cursor
Editor and terminal

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 Cursor 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 Cursor

    Add the gateway to Cursor in one click from the Organization Gateway page.

    On the Organization Gateway page in Speakeasy, choose Cursor under Install.

    Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.

  4. 04

    Sign in and use Fireflies from Cursor

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

For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.

Use cases

What Cursor users do with Fireflies

Recover a detail from a design review

Ask Cursor what the designer said about an empty state or an error message, and it searches recent meetings and quotes the relevant lines.

fireflies_searchfireflies_fetch

Browse the team's meeting folders

Cursor lists the channels you can access, such as one folder per product area, and shows who belongs to each, so you know where related calls live.

fireflies_list_channelsfireflies_get_channel

Clip a demo for the pull request

After a demo call, have Cursor create a soundbite covering the minutes where the feature was shown, and link it from the pull request description.

fireflies_create_soundbite

Tools

19 tools

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

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

Prompt and tool-call blocking

Cursor

Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.

User attribution

Cursor

Every Cursor hook event carries the user's email.

Budgets

Cursor

Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.

Device agent and MDM

Cursor

The device agent installs the marketplace and plugins and reapplies them every minute.

  • Cursor Cloud agents need a checked-in .cursor/hooks.json. Session and MCP-specific hooks don't run there.
  • After a plugin update, members run Developer: Reload Window.

Questions

Frequently asked questions

Do developers need a Fireflies API key in Cursor?
No. Sessions authenticate through your identity provider, and agents never hold a Fireflies credential. Access ends when the employee leaves the directory.
Do Fireflies controls apply to Cursor Cloud agents?
Cursor Cloud agents need a checked-in .cursor/hooks.json. Session and MCP-specific hooks don't run there.
How do Cursor users get Fireflies?
An admin adds Fireflies from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway to Cursor in one click from the Organization Gateway page. Each person then sees only the Fireflies tools their access allows.
Are Fireflies calls from Cursor 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.