Fireflies

Search Fireflies transcripts and summaries.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Fireflies connector does

The Fireflies MCP server connects a Fireflies.ai meeting archive to Claude, ChatGPT, Claude Code and any MCP-compatible agent. It searches transcripts, opens them with speakers and timestamps, and pulls summaries into a model's context. Two things make it unusual: Fireflies documents nineteen tools where the directory lists three, and its reach depends on whose credential you connect.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Fireflies tools (3)

  • get_user
  • get_transcript
  • get_transcripts

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The directory listing undercounts by a wide margin. It lists three tools where Fireflies documents nineteen, and names them without the fireflies_ prefix the vendor reference uses. Build allowlists from Fireflies' documentation, not the listing.
  • The "Read" permissions label does not describe the documented server. Fireflies documents five tools that act: share, revoke share, rename, move and create a clip. The label is accurate only for the three-tool subset the snapshot carries.
  • One tool sends meeting content outside the workspace. fireflies_share_meeting shares a transcript with up to 100 email addresses in one call. Fireflies documents the caller as needing to own the meeting or be a team admin.
  • Reach depends on the connected account's role. Fireflies states the Super Admin API bypasses the team's privacy settings and queries all data in the account, on Enterprise only and behind a signed agreement. The connector inherits that; it does not narrow it.
  • The MCP guide and the API docs describe different scopes, and both are current. The guide says only the user's meetings are reachable with their own key; the Super Admin page says otherwise for that role. Read the guide as being about ordinary keys.
  • An API key does not expire on a session boundary. Fireflies documents key generation in Developer settings and a bearer header, and publishes no expiry. A key in a config file outlives the sitting.
  • The advertised scopes cannot express data access. profile and email only. Nothing at authorization time distinguishes reading a summary from sharing a transcript.
  • We could not verify tool behaviour ourselves. The endpoint returns 401 to an anonymous handshake, so no schemas and no safety annotations were readable to us.
  • Two tools may not exist on your account. Fireflies marks fireflies_search and fireflies_fetch as experimental and progressively rolled out, possibly behind a feature flag.
  • One tool is plan-gated. fireflies_get_rule_executions is documented as requiring Enterprise.
  • Results are capped at 50 per query. Fireflies documents that ceiling on both the MCP tool and the underlying GraphQL query, with an offset for pagination.
  • Analytics profile people, not meetings. fireflies_get_analytics returns per-user sentiment, talk-listen ratio, monologue and filler-word metrics; team-level figures require admin privileges.
  • There is no deletion tool over MCP. Fireflies' API documents transcript deletion, but no deletion tool appears in the MCP reference, so retention cannot be managed from an agent.
  • Retention is manual, not scheduled. Fireflies states users can delete data at any time; it does not document an auto-deletion window for transcripts the way some peers do.
  • Prompts are unconfirmed. Anthropic's snapshot lists no prompt names, but the gated endpoint blocked our own prompts/list, so we cannot say whether the server serves any.
  • The connector adds no consent check. Fireflies joins calls as a visible bot, which is the notice mechanism, but nothing in the MCP layer verifies that participants understood a transcript would be made or read by an agent.

Frequently asked questions

Whose meetings can the Fireflies MCP connector read?

It depends entirely on whose credential you connect, because the key inherits that person's role. An ordinary member reaches their own meetings. Fireflies documents an Enterprise-only Super Admin role whose API access bypasses the team's privacy settings and queries all data in the account. Connect a Super Admin key and the reachable corpus becomes the whole workspace.

Can the Fireflies MCP server write or change anything?

Yes, despite the directory's Read label. Fireflies documents five tools that act: fireflies_share_meeting, fireflies_revoke_meeting_access, fireflies_update_meeting_title, fireflies_move_meeting and fireflies_create_soundbite. Sharing sends a transcript to up to 100 email addresses. The directory snapshot lists only three read tools, so its permissions label describes that subset rather than the documented server.

How many tools does the Fireflies MCP server actually have?

Nineteen by Fireflies' own reference, against three in Anthropic's directory snapshot. The snapshot names get_user, get_transcript and get_transcripts. Fireflies documents nineteen tools all carrying a fireflies_ prefix, covering search, summaries, channels, soundbites, analytics, contacts and rule logs. Two of the nineteen are marked experimental and may need a feature flag. Build allowlists from the vendor reference.

Does the Fireflies MCP server accept an API key instead of OAuth?

Yes. Fireflies documents both an OAuth flow and an API key passed as a bearer token in an Authorization header. That matters because an API key is a credential rather than a person: it carries whatever role its owner holds, has no per-user narrowing, and does not lapse the way a browser OAuth session does when someone leaves.

What can get_transcripts filter or search over?

Fireflies documents structured filters on the transcripts query and its MCP equivalent: a keyword capped at 255 characters, a search scope of title, sentences or all, a fromDate and toDate range, arrays of organizers and participants, a host email, a user id, a channel id, and a mine boolean. Results are capped at 50 per query with skip for pagination.

Does Fireflies train AI models on my meeting transcripts?

Fireflies states it does not train on customer data by default and describes a zero-day retention policy with its vendors and partners, so meeting data is not used for model training. It also states users keep full control of transcripts and can delete them at any time. Fireflies names SOC 2 Type II, GDPR and Enterprise-only HIPAA BAA coverage.

What OAuth scopes does Fireflies MCP request?

Only two, and neither describes data. The live protected-resource descriptor advertises profile and email — pure identity scopes with no meeting, transcript or write scope alongside them. So the authorization screen cannot express what an agent will reach. Access is decided afterwards by the connected account's Fireflies role, not by anything a client negotiates at sign-in.

Do meeting participants know Fireflies is recording?

Fireflies joins calls as a visible bot participant, which is the notice mechanism: it appears in the attendee list the way a person does. That is a product behaviour rather than an MCP one. The connector adds no consent check of its own — it will return a transcript regardless of what anyone in the room understood at the time.

Sources

  • Learn about the Fireflies MCP Server — https://guide.fireflies.ai/articles/8272956938-learn-about-the-fireflies-mcp-server-model-context-protocol (fetched 2026-08-19) · retrieved 2026-08-19
  • MCP Tools reference — https://docs.fireflies.ai/mcp-tools/overview (fetched 2026-08-19 as Markdown via the .md suffix; nineteen tools, five of them writes) · retrieved 2026-08-19
  • MCP Server Configuration — https://docs.fireflies.ai/getting-started/mcp-configuration (fetched 2026-08-19; OAuth and bearer API key both documented) · retrieved 2026-08-19
  • Super Admin — https://docs.fireflies.ai/fundamentals/super-admin (fetched 2026-08-19; privacy-setting bypass, Enterprise only) · retrieved 2026-08-19
  • Learn about the Super Admin role — https://guide.fireflies.ai/articles/7734409426-learn-about-the-super-admin-role (fetched 2026-08-19; side letter required, removal via support) · retrieved 2026-08-19
  • transcripts query — https://docs.fireflies.ai/graphql-api/query/transcripts (fetched 2026-08-19; filter list and the 50-result cap) · retrieved 2026-08-19
  • Fireflies API overview and how to get an API key — https://guide.fireflies.ai/articles/3737786777-fireflies-api-overview-get-api-key (fetched 2026-08-19; API available regardless of plan level) · retrieved 2026-08-19
  • Fireflies security — https://fireflies.ai/security (fetched 2026-08-19; no training by default, zero-day vendor retention, SOC 2 Type II, GDPR, Enterprise HIPAA BAA) · retrieved 2026-08-19
  • Fireflies docs machine index — https://docs.fireflies.ai/llms.txt (fetched 2026-08-19) · retrieved 2026-08-19
  • docs.fireflies.ai/robots.txt disallows only /cdn-cgi/ and /_next/, names a sitemap, and carries Content-Signal: ai-train=yes, search=yes, ai-input=yes — the publisher expressly permits AI input as well as search (fetched 2026-08-19). guide.fireflies.ai/robots.txt is a generic allowlist template with no Content-Signal · retrieved 2026-08-19
  • Live RFC 9728 protected-resource descriptor — https://api.fireflies.ai/.well-known/oauth-protected-resource/mcp (fetched 2026-08-19; the root form returns a byte-identical body, the path-insert form returns 404) · retrieved 2026-08-19
  • Live RFC 8414 authorization-server metadata — https://api.fireflies.ai/.well-known/oauth-authorization-server (fetched 2026-08-19; the same two identity scopes, no data scope) · retrieved 2026-08-19
  • Live anonymous probe — 2026-08-19: a POST to the endpoint returns HTTP 401 with www-authenticate naming scope="email profile" and resource_metadata at the path-append well-known URL · retrieved 2026-08-19
  • Anthropic connector directory — https://claude.ai/directory/839a0ae2-0c0f-4c27-9f85-726ed6515536 (snapshot 2026-08-16) · retrieved 2026-08-16

More Communication connectors

  • AgentMail

    Give an AI agent its own email inbox: create inboxes, read threads and send mail to anyone.

  • Circleback

    Search meeting notes, transcripts, action items, calendar and connected email.

  • Fellow.ai

    Pull meeting transcripts, summaries, action items and participants from Fellow.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Fireflies to work.

Connect Fireflies once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.