MCP Gateway · Claude Cowork
Connect Fireflies to Claude Cowork
Cowork can take on the meeting chores nobody gets to: reviewing a quarter of calls, filing them, writing up patterns. With Fireflies synced in as a plugin, a session can search transcripts, read summaries and act on what it finds over many steps. Agent hooks check each prompt with Speakeasy before the step runs.
- Category
- Communication
- Tools
- 19
- Authentication
- OAuth
- Claude Cowork
- Cowork tab in Claude Desktop
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 Cowork 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. Claude Cowork 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 Claude Cowork
Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.
New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.
Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.
In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.
Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.
In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.
- 04
Sign in and use Fireflies from Claude Cowork
The first time Claude Cowork 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 Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.
Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
Use cases
What Claude Cowork users do with Fireflies
Write a voice-of-customer report
Cowork searches the quarter's customer calls for feature requests and complaints, reads each relevant transcript in full, and writes a report grouped by theme with quotes.
File a backlog of meetings
Cowork lists the team's channels, works through unfiled meetings five at a time, and moves each one into the folder for its customer or project.
Audit automation rules on meetings
On Fireflies Enterprise, Cowork reviews rule execution logs to see which meetings were shared, moved or had their privacy changed, and flags anything unexpected.
Tools
19 tools
Each Fireflies tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork 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 Cowork
The gateway covers every client the same way. The rest depends on what Claude Cowork 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 Cowork. MCP-scoped policies are enabled per organization.
Prompt blocking
Claude Cowork
Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.
Session telemetry
Claude Cowork
Cowork's OTLP export ties sessions to people and feeds observability.
Anthropic inference hooks
Claude Cowork
On Claude Enterprise, prompts can be checked before inference (beta).
- Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
- Personal Claude accounts can't be governed in Cowork.
Questions
Frequently asked questions
Can a Cowork session change who sees a meeting?
Is Fireflies in Cowork covered by the device agent?
How do Claude Cowork users get Fireflies?
Are Fireflies calls from Claude Cowork logged?
Connect more