Secure Fireflies access for AI agents

AI meeting notetaker — search transcripts, fetch summaries and action items, and manage recordings and channels via Fireflies' official MCP server.

Through Fireflies, agents can search and read meeting transcripts, pull AI-generated summaries and action items, and manage recordings, channels, and sharing — without a custom integration. Every call runs through your policies and is logged for audit.

Server URL: https://api.fireflies.ai/mcp

Setup

Navigate to Resources and click Add Resource
Select Fireflies from the catalog
Choose Per-org dynamic registration, the only mode Fireflies offers — picking the card installs the resource with all tools and scopes pre-configured, registering an OAuth client with Fireflies as it goes

Each user connects their own Fireflies account via OAuth when they first use a Fireflies tool. Navigate to Connections to manage linked accounts.

Fireflies' registration endpoint does not return an RFC 7592 management token: OAuth clients created by dynamic registration cannot be updated or deleted through the API afterwards. Removing the resource orphans the registered client on Fireflies' side.

Credential modes

Fireflies uses Dynamic Client Registration (RFC 7591) only — the gateway registers a per-organization OAuth client with Fireflies automatically on first install. SecureAuth-app and Bring-your-own-app modes are not available for this resource. See Credential modes for how this compares to other catalog resources.

Dynamic client registration

This is the mode card labeled Per-org dynamic registration on the Fireflies configure page. The gateway registers its OAuth client with Fireflies at install time — no client ID or secret to configure. Each user then connects their own Fireflies account via a browser OAuth flow the first time they use a Fireflies tool.

Required scopes

Fireflies uses a fixed identity scope pair — authorization is identity-based, and which meetings and data an agent can reach mirrors the signed-in user's Fireflies account rather than OAuth scope grants.

Scope	Why
`profile`	Access to profile information
`email`	Access to the account's email address

Refresh tokens are issued, so connections rarely require re-auth.

Available tools

Tool	Access	Description
`fireflies_search`	read	Advanced transcript search using Fireflies' mini-grammar syntax
`fireflies_get_transcripts`	read	List transcripts with filters (keyword, dates, participants)
`fireflies_get_transcript`	read	Fetch a transcript by ID with sentences, speakers, timestamps
`fireflies_fetch`	read	Retrieve complete meeting data (transcript, summary, metadata)
`fireflies_get_summary`	read	Fetch a meeting summary with action items and keywords
`fireflies_get_active_meetings`	read	List currently active, in-progress meetings
`fireflies_get_analytics`	read	Team and per-user meeting conversation analytics
`fireflies_share_meeting`	write	Share a meeting transcript with given email addresses
`fireflies_revoke_meeting_access`	write	Revoke previously shared access to a meeting
`fireflies_update_meeting_title`	write	Update the title of a meeting transcript
`fireflies_move_meeting`	write	Move transcripts into a channel/folder
`fireflies_list_channels`	read	List channels/folders available to the user
`fireflies_get_channel`	read	Retrieve a channel/folder by ID
`fireflies_get_soundbites`	read	Fetch shareable soundbite clips from meetings
`fireflies_create_soundbite`	write	Create a soundbite clip from a transcript
`fireflies_get_user`	read	Fetch user account details
`fireflies_get_usergroups`	read	Fetch user groups for the user or team
`fireflies_get_user_contacts`	read	Fetch the contact list by most recent meeting
`fireflies_get_rule_executions`	read	Retrieve automation rule execution logs

The gateway picks up the live tool set from the server after the first connection, so any tools Fireflies adds or renames surface automatically.

Policy examples

Every org is created with a seeded Allow all rule at the bottom of the list, so any call your own rules don't match stays allowed. Express restrictions as deny rules above it — new rules are added at the top, so a fresh deny outranks it automatically. See Rule order.

Read-only access: deny the write tools — fireflies_share_meeting, fireflies_revoke_meeting_access, fireflies_update_meeting_title, fireflies_move_meeting, and fireflies_create_soundbite. What remains is search, transcript, summary, analytics, and channel reads.
No external sharing: deny fireflies_share_meeting and fireflies_revoke_meeting_access so agents can read meetings but never change who else can.
No organizational edits: deny fireflies_move_meeting and fireflies_update_meeting_title to keep agents from reorganizing or renaming the team's recordings.

Next steps

Create a policy — start from the read-only pattern in Policy examples above.
Credential modes — see how DCR compares to the other modes catalog resources use.