MCP Gateway · OpenCode
Connect Fireflies to OpenCode
With Fireflies added as a remote server, OpenCode can read meeting data from the terminal. Developers use it to check what's happening on a call, or who they last spoke with, without switching to a browser. The OpenCode plugin sends each prompt and tool call to Speakeasy for an allow or deny decision, and the device agent maintains the observability package.
- Category
- Communication
- Tools
- 19
- Authentication
- OAuth
- OpenCode
- 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.
Set up
Add Fireflies to OpenCode 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. OpenCode connects to the Fireflies server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect OpenCode
Add the server to OpenCode's own mcp config block as a remote server.
Copy the server's URL from its hosted install page in Speakeasy.
Add it to the
mcpblock of your OpenCode config withtypeset toremote.Restart OpenCode and sign in when prompted.
{ "mcp": { "<server slug>": { "type": "remote", "url": "<URL from the hosted install page>" } } } - 04
Sign in and use Fireflies from OpenCode
The first time OpenCode 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 OpenCode, limited to what the person's access allows, and every call lands in the gateway's tool logs.
OpenCode doesn't receive MCP servers from plugins. The observability package is installed separately, from a ZIP or with speakeasy-hooks install --provider=opencode, and the device agent can maintain it.
Use cases
What OpenCode users do with Fireflies
Read a live incident call
During an incident bridge, OpenCode fetches a snapshot of the live transcript captured so far and summarizes what's been tried, while you stay in the shell.
Check your in-progress meetings
Ask OpenCode which of your meetings are running right now, with titles, organizers and meeting links, before deciding whether to join or keep coding.
Look up recent meeting contacts
OpenCode lists your Fireflies contacts sorted by most recent interaction, with names and emails, so you can find who to ask about a service you're changing.
Tools
19 tools
Each Fireflies tool can be allowed or denied per team and role at the MCP Gateway before OpenCode 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 OpenCode
The gateway covers every client the same way. The rest depends on what OpenCode 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 OpenCode. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
OpenCode
The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs.
Usage telemetry
OpenCode
Token and cost totals flow through the plugin, reported per turn.
Device agent
OpenCode
The device agent installs and maintains the observability package.
- OpenCode has no OpenTelemetry exporter, so session data comes through the plugin.
- Tool output is blocked at the gateway rather than in OpenCode's hooks.
Questions
Frequently asked questions
How does OpenCode report usage without OpenTelemetry?
Can OpenCode see other people's meetings?
How do OpenCode users get Fireflies?
Are Fireflies calls from OpenCode logged?
Connect more