Fireflies MCP server for your AI

One personal API key, copied from Integrations, Fireflies API in your Fireflies account. There is no OAuth app to create. The key is one Fireflies user: the MCP sees and does what that user can, on that team's plan, and the connection stays locked to that account. Some tools need more than a regular seat, such as team analytics and set_user_role, so connect an admin's key if the AI should use those.

Any plan connects, but the limits differ: Free allows 50 API requests a day, Pro 500 a day, and Business and up 60 a minute. Recording links from transcript_media and upload_audio need Pro or higher, team analytics needs Business and admin rights, and audit_events needs Enterprise. PopMCP keeps those plan-gated fields in their own tools, so a free plan can still read summaries and transcripts without the whole call failing.

Yes. add_to_live_meeting sends the bot into a running Zoom, Google Meet, Microsoft Teams or other supported call, so it records from that point; Fireflies allows 3 of these calls every 20 minutes. active_meetings lists the calls the bot is in, update_meeting_state pauses or resumes recording, and create_live_action_item and create_live_soundbite file items or clips in plain English while the call runs, at 10 an hour and using AI credits.

Yes, from a link. upload_audio takes a direct HTTPS URL to an mp3, mp4, wav, m4a or ogg file, and Fireflies downloads it itself, so a local file path or a share or preview page will not work; a signed download URL does. It needs a Pro or higher plan, and audio is capped at 200 MB. The upload is queued rather than finished, so the AI checks transcripts afterwards for the completed meeting.

AskFred is Fireflies' own AI for questions about your meetings. create_askfred_thread asks a question about one meeting or across many with filters, continue_askfred_thread follows up with the earlier answers as context, and askfred_threads and askfred_thread read past conversations. The answer is generated on Fireflies' side. When the meeting summary already holds what you need, transcript_summary is the cheaper read, and transcript_sentences gives the exact words.

Twelve. Polling fires when a meeting finishes and its transcript and summary are ready. Change detection covers the notetaker joining a live meeting, a new soundbite, someone new appearing on a call, a new channel, a new teammate, a user group change, a new AskFred thread and a new AI App result. From the audit log it also catches a meeting being shared or deleted and a team automation rule changing a meeting.

No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.

Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.

Connect Fireflies in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking Fireflies on the consent screen. The Fireflies tools are then available in that session, and no Fireflies credential is stored on your machine.

Yes. The Fireflies catalog is small enough that all 38 tool definitions load into every conversation, so your AI never has to search for one before it can call it.

A tool is something your AI calls, and there are 38 here. A trigger is something PopMCP watches for you: 12 Fireflies events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Fireflies.