Connect your AI Agents to Fireflies in minutes

What is a Fireflies MCP server?

It’s an MCP server that lets you access data and functionality from Fireflies via tools. Your agents can invoke these tools to get meeting analytics, upload an audio file, update meeting titles, and more. 

Fireflies offers their own “official” MCP server. You can also access additional Fireflies MCP servers from 3rd-party platforms, like Merge Agent Handler.

How can I use a Fireflies MCP server?

Here are some common use cases:

• Meeting intelligence on demand: Pull your latest Fireflies meeting, summarize it, and surface decisions, risks, and open questions

• Action item extraction and routing: Turn “next steps” into structured tasks, assign owners, and push them into your task tracker with meeting links and context

• CRM auto-updates after calls: After sales or CS calls, auto-log notes, update fields, and create follow-ups in Salesforce/HubSpot based on what was actually said

• Deal and pipeline hygiene: Detect missing next steps, unclear timelines, or stalled deals from call transcripts and prompt reps to fix the CRM record

• Customer support escalation: Identify bugs, outages, or high-severity complaints in calls, then create/append support tickets with transcript excerpts

What are popular tools for Fireflies’ MCP server?

Here are some widely-used tools:

• <code class="blog_inline-code">list_meetings</code>: Core for discovering meetings in your workspace; use it to fetch recent or filtered meetings before doing anything else (transcripts, notes, tasks, etc.)

• <code class="blog_inline-code">get_transcript</code>: Main way to extract detailed conversational data from a meeting; powers analytics, QA, search, and downstream NLP

• <code class="blog_inline-code">get_notes</code>: Quickly access AI-generated summaries and action items from a meeting without parsing the full transcript

• <code class="blog_inline-code">upload_audio</code>: Key ingestion endpoint if you’re bringing your own recordings (outside calendar/autojoin), to generate transcripts and notes
  

• <code class="blog_inline-code">webhook_subscribe</code>: Essential for automation: lets your system react when meetings finish, transcripts are ready, or notes are generated, without polling

What makes Merge Agent Handler’s Fireflies MCP server better than alternative Fireflies MCP servers?

Merge Agent Handler provides platform-level advantages:

• End-to-end integration lifecycle management: Merge handles authentication, credential management, rate limiting, and error handling across connectors, reducing infrastructure overhead for developers

• Enterprise-grade security with DLP: A built-in security gateway scans tool inputs and outputs for sensitive data and can block or redact information based on configured rules

• Real-time observability and auditability: Every tool call is logged with a fully-searchable audit trail, enabling debugging, monitoring, and compliance tracking

• Connector Studio for extensibility: Developers can modify existing connectors or build custom tools tailored to their Fireflies workflows while maintaining production-grade reliability

• Evaluation Suite for pre-production validation: Tools can be tested against expected outcomes before deployment, improving reliability and agent performance

Can I set custom security rules for Fireflies tool calls in Merge Agent Handler?

Yes, Merge Agent Handler includes a security gateway with configurable rules that scan tool inputs and outputs for sensitive data and take action (e.g., block, redact, or mask).

You can also define custom data protection rules tailored to your use case and enforce them across all tool interactions. Here are a few examples:

• ‍Approval gate for external sharing: Require human approval if an agent tries to share Fireflies meeting notes or transcripts outside approved domains or channels

• Scoped retrieval allowlist: Only allow agents to fetch Fireflies data for approved meetings, calendars, teams, or projects; deny everything else by default

• RBAC for Fireflies tools: Limit who can run Fireflies actions by role, and enforce least privilege on what each role can access or export

• Incident alerting and audit trail: On any Fireflies policy violation, alert the right team and record the attempted action, rule hit, and actor in an auditable log with retention controls

How can I start using Merge Agent Handler’s Fireflies MCP server?

1. Create (or sign in to) your Merge Agent Handler account and open the dashboard.

2. Get your Agent Handler API key since your MCP client will use it as a bearer token to authenticate to the Agent Handler MCP endpoint.

3. Create a Tool Pack for the Fireflies workflow you want to power since Tool Packs define which connectors and tools your agent is allowed to use.

4. Add the Fireflies connector to that Tool Pack and start by enabling only the specific tools you need.

5. Create a Registered User (or decide on a service-account pattern) since this is the identity boundary Agent Handler uses to scope credentials and audit logs.

6. Complete the Fireflies authentication flow for that Registered User using Merge Link or Magic Link so Fireflies tool calls run under the right permissions without you managing tokens directly.

7. Copy the MCP endpoint URL for your Tool Pack and Registered User in the format <code class="blog_inline-code">.../tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp</code>.

8. Add that MCP server URL to your MCP client (Cursor, Claude Desktop, VS Code, Windsurf, and so on) and configure it to send <code class="blog_inline-code">Authorization: Bearer <AGENT_HANDLER_API_KEY></code> on requests to that MCP URL.

8. Test with <code class="blog_inline-code">list_tools</code> and a simple read action, then verify behavior in logs or the Playground, then tighten Tool Pack scope and security rules before production use.