Skip to main content
Back to the Fireflies MCP server

MCP Gateway · Codex

Fireflies icon

Connect Fireflies to Codex

Long Codex tasks go better with context from the people who asked for the work. Fireflies lets Codex search meeting transcripts and summaries for requirements, so a spec discussed on a call reaches the code. Speakeasy's agent hooks check every prompt and tool call before Codex acts, and the device agent keeps Codex's configuration in sync on managed laptops.

Category
Communication
Tools
19
Authentication
OAuth
Codex
CLI and ChatGPT desktop app

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

    Add the gateway as an MCP server, then log in.

    Run the first command with your organization gateway URL.

    Run the second command to sign in.

    codex mcp add 'speakeasy' \
      --url 'https://<organization host>/mcp/gateway/<organization slug>'
    codex mcp login 'speakeasy'
  4. 04

    Sign in and use Fireflies from Codex

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

To roll it out to a team, a ChatGPT workspace admin imports the plugin marketplace under Admin > Plugins and sets an installation policy per role. Imported plugins reach nobody until a policy is set.

Use cases

What Codex users do with Fireflies

Pull requirements from a planning call

Give Codex the date and topic of a planning meeting. It filters transcripts to find the call, then reads the summary for requirements before starting the task.

fireflies_get_transcriptsfireflies_get_summary

Find every call that mentioned an endpoint

Codex runs a keyword search across meeting sentences for an endpoint or feature name in a date range, so a deprecation plan accounts for everyone who raised it.

fireflies_search

Draft a postmortem from the incident call

After an incident bridge, Codex reads the transcript with its speakers and drafts the postmortem sequence of events in the repo's docs folder.

fireflies_get_transcript

Tools

19 tools

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

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

Prompt and tool-call blocking

Codex

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

User attribution

Codex

An [otel] block in ~/.codex/config.toml sends telemetry to Speakeasy. Export is off by default.

Budgets

Codex

Spend limits can block Codex traffic once a budget is reached.

Device agent and MDM

Codex

The device agent keeps Codex's configuration in sync on managed laptops.

  • Codex cloud tasks and GitHub code review run off the device. Neither the plugin nor OpenTelemetry covers them; OpenAI's Compliance Logs record them after the fact.
  • The workspace rollout needs a ChatGPT Business, Enterprise or Edu admin.

Questions

Frequently asked questions

Are Codex cloud tasks that read Fireflies covered?
Codex cloud tasks and GitHub code review run off the device, so neither the plugin nor OpenTelemetry covers them. OpenAI's Compliance Logs record them after the fact.
Can meeting content be redacted before Codex sees it?
PII redaction runs on every Fireflies tool call at the gateway, along with prompt injection detection. Which Fireflies tools a team can call is also set there.
How do Codex users get Fireflies?
An admin adds Fireflies from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway as an MCP server, then log in. Each person then sees only the Fireflies tools their access allows.
Are Fireflies calls from Codex 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.