Fireflies Claude integration over MCP

Start with a date-filtered meeting search and read the selected transcript by ID. A title or summary is not a substitute for the actual conversation when you need evidence of an agreed decision. Ask for speaker and timestamp context, with a link to the relevant recording moment when available.

Summary and transcript tools return different material. Use get_summary for action items and overview; use detailed transcript retrieval for exact wording. A meeting summary can omit qualifications, so an agent should not turn a tentative idea into an approved decision without checking the source.

The connected user’s role matters. Team analytics require appropriate privileges, and organizational access does not mean every private meeting becomes visible. Ask the agent to state when the requested meeting is inaccessible rather than searching unrelated records for a plausible replacement.

Fireflies MCP server: official and alternate routes

The Fireflies tool documentation describes official capabilities and access requirements. A separate Fireflies CLI project is another implementation route; it is not evidence that every CLI feature exists in the remote MCP catalog.

Direct Fireflies is simpler for one meeting client. AIPx is useful when meeting context informs Notion, Linear or email follow-ups. It adds another processor for transcript data, which can be sensitive even when every enabled tool is read-only.

Connect Fireflies to Claude, Claude Code, Cursor or Codex

Choose Fireflies and complete its official OAuth flow. Inspect the authenticated user’s available tools and provider plan before promising transcript or analytics access.

1. Open the AIPx dashboard, choose Fireflies under Integrations and complete its connection form or authorization.
2. Create an MCP agent, enable that connection and choose the tools this particular agent needs. Save the rules before opening your AI client.
3. Copy the agent’s complete URL. The examples below use AGENT_ID; replace it with the actual value from your dashboard.

An endpoint identifies the AIPx agent, not a provider API key. Client authentication to AIPx is separate from connecting Fireflies; adding the URL does not grant extra provider permissions. Our MCP gateway guide explains how several approved connections can share that endpoint.

Connect Claude to Fireflies

In Claude, open Customize → Connectors and add a custom connector with your AIPx URL. Continue through AIPx sign-in, then check the tools available in a conversation. Custom connector access depends on account and workspace policy; administrators can restrict it. The Claude MCP setup guide covers the current controls. A direct vendor connection can be simpler when Fireflies is the only service you need.

Fireflies MCP in Claude Code

claude mcp add --transport http aipx https://dash.aipx.run/mcp/AGENT_ID

Run /mcp to authorize, then find a dated Fireflies meeting and fetch it by ID. Cite transcript timestamps before drawing a conclusion. Claude Code MCP setup explains login and configuration.

Fireflies MCP in Cursor

Add this server to .cursor/mcp.json for the project or ~/.cursor/mcp.json for your user:

{
  "mcpServers": {
    "aipx": { "url": "https://dash.aipx.run/mcp/AGENT_ID" }
  }
}

After Cursor sign-in, retrieve the relevant incident transcript rather than broad team analytics. Keep returned source links in the diagnosis. See Cursor MCP setup for server discovery and config scope.

Fireflies MCP in Codex

codex mcp add aipx --url https://dash.aipx.run/mcp/AGENT_ID
codex mcp login aipx
codex mcp list

Codex uses the HTTP endpoint and browser OAuth; it does not need a copy of the Fireflies credential in its config. See Codex MCP setup for TOML configuration and project trust requirements.

Custom ChatGPT MCP can use the Fireflies endpoint when the account and workspace permit it. Meeting visibility still follows Fireflies access. The ChatGPT MCP guide explains the client’s separate eligibility requirements.

Scope Fireflies per agent

A meeting researcher can use transcript discovery and details, while a follow-up assistant may only need summaries. Hide contacts, user groups or broad analytics when the task does not need them. If newly discovered writes appear, keep them hidden until an actual task requires them.

General reads start on Allow, but the recommendation should follow the sensitivity of the returned data. MCP permissions helps restrict the callable surface; it does not change the provider’s privacy settings for the meeting itself.

Granola is a separate meeting-notes connection. Gmail and Apple Calendar can identify the invitation, while AgentMail can send a reviewed follow-up through a separately configured inbox.

Fireflies transcript and account limits

Use records and transcripts available to the authenticated account. This connection does not promise to start recording or transcribing a new meeting, or expose every meeting in an organization. A live transcript, where the provider supplies one, is only a point-in-time snapshot.

Analytics, automation logs and experimental search can have role or plan conditions. Provider quotas still apply. When retrieval fails, check the meeting ID and access rather than treating the missing transcript as proof that no decision was made.

Browse all MCP integrations to choose another connection for this agent.

The Fireflies connection can use AIPx Free with 3 active accounts and 1 agent; check AIPx pricing for gateway plans and keep provider or client charges separate.