# Fireflies.ai

> Official Fireflies remote MCP — query meeting transcripts, AI summaries, and action items via OAuth or API key.

[Canonical HTML page](https://top-mcps.com/mcp/fireflies) · [server.json](https://top-mcps.com/mcp/fireflies.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

Paste under mcpServers. Fully quit and reopen Claude after editing.

```json
{
  "mcpServers": {
    "fireflies": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.fireflies.ai/mcp",
        "--header",
        "\"Authorization:",
        "Bearer",
        "YOUR_FIREFLIES_API_KEY\""
      ],
      "env": {
        "FIREFLIES_API_KEY": "${FIREFLIES_API_KEY}"
      }
    }
  }
}
```

### Claude Code — `CLI or .mcp.json`

Run from your repo. Commit .mcp.json to share with your team.

```shell
# export FIREFLIES_API_KEY=your_fireflies_api_key
claude mcp add fireflies -- npx mcp-remote https://api.fireflies.ai/mcp --header "Authorization: Bearer YOUR_FIREFLIES_API_KEY"
```

### Cursor — `.cursor/mcp.json`

Global path: ~/.cursor/mcp.json. Reload window after editing.

```json
{
  "mcpServers": {
    "fireflies": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.fireflies.ai/mcp",
        "--header",
        "\"Authorization:",
        "Bearer",
        "YOUR_FIREFLIES_API_KEY\""
      ],
      "env": {
        "FIREFLIES_API_KEY": "${FIREFLIES_API_KEY}"
      }
    }
  }
}
```

### VS Code — `.vscode/mcp.json`

VS Code uses the "servers" key (not "mcpServers").

```jsonc
{
  "servers": {
    "fireflies": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.fireflies.ai/mcp",
        "--header",
        "\"Authorization:",
        "Bearer",
        "YOUR_FIREFLIES_API_KEY\""
      ],
      "env": {
        "FIREFLIES_API_KEY": "${FIREFLIES_API_KEY}"
      }
    }
  }
}
```

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

```json
{
  "mcpServers": {
    "fireflies": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.fireflies.ai/mcp",
        "--header",
        "\"Authorization:",
        "Bearer",
        "YOUR_FIREFLIES_API_KEY\""
      ],
      "env": {
        "FIREFLIES_API_KEY": "${FIREFLIES_API_KEY}"
      }
    }
  }
}
```

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

```json
{
  "mcpServers": {
    "fireflies": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.fireflies.ai/mcp",
        "--header",
        "\"Authorization:",
        "Bearer",
        "YOUR_FIREFLIES_API_KEY\""
      ],
      "env": {
        "FIREFLIES_API_KEY": "${FIREFLIES_API_KEY}"
      }
    }
  }
}
```

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

```json
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "mcp-remote",
            "https://api.fireflies.ai/mcp",
            "--header",
            "\"Authorization:",
            "Bearer",
            "YOUR_FIREFLIES_API_KEY\""
          ],
          "env": {
            "FIREFLIES_API_KEY": "${FIREFLIES_API_KEY}"
          }
        }
      }
    ]
  }
}
```

### Codex CLI — `~/.codex/config.toml`

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

```shell
# ~/.codex/config.toml
[mcp_servers.fireflies]
command = "npx"
args = [
  "mcp-remote",
  "https://api.fireflies.ai/mcp",
  "--header",
  "\"Authorization:",
  "Bearer",
  "YOUR_FIREFLIES_API_KEY\"",
]
env = { FIREFLIES_API_KEY = "${FIREFLIES_API_KEY}" }
```

### Zed — `~/.config/zed/settings.json`

Zed calls them "context_servers". Settings live-reload on save.

```jsonc
{
  "context_servers": {
    "fireflies": {
      "command": {
        "path": "npx",
        "args": [
          "mcp-remote",
          "https://api.fireflies.ai/mcp",
          "--header",
          "\"Authorization:",
          "Bearer",
          "YOUR_FIREFLIES_API_KEY\""
        ]
      },
      "env": {
        "FIREFLIES_API_KEY": "${FIREFLIES_API_KEY}"
      }
    }
  }
}
```

### ChatGPT — `ChatGPT → Settings → Connectors (remote URL)`

Paste this into Settings → Connectors → Add custom connector. Requires ChatGPT Pro / Team / Enterprise / Edu with Developer mode enabled. ChatGPT supports remote HTTPS MCP servers only — stdio servers must be hosted on a public HTTPS endpoint first.

```json
{
  "name": "Fireflies.ai",
  "transport": "http",
  "url": "https://api.fireflies.ai/mcp"
}
```

## At a glance

- **Maintainer:** Fireflies.ai
- **Transport:** Streamable HTTP
- **Auth model:** OAuth 2.1
- **Required secrets:** FIREFLIES_API_KEY
- **Supported clients:** Claude, Cursor, ChatGPT, Any MCP-compatible client
- **License:** Proprietary
- **Last verified:** 2026-06-11
- **Score:** 54/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Homepage:** https://fireflies.ai/blog/fireflies-mcp-server/

## Security & scope

- **Access scope:** read-only
- **Sandbox:** Hosted by Fireflies. OAuth or Bearer-token scoped to the connecting user. No local recording or file access.
- **Gotchas:**
  - API keys grant access to every meeting the user can see — rotate if a developer with a personal key leaves the team.
  - Workspace admins can disable third-party API access globally; if calls return 401, check workspace settings before debugging the client.

## Quick answer

**What it does.** Surfaces Fireflies meeting transcripts, AI-generated summaries, action items, and search across past calls as MCP tools. Hosted by Fireflies; OAuth or API-key authenticated.

**Best for:**
- Cross-meeting topic search
- AI summaries on demand
- Pulling action items into other tools
- Sales call recall
- Customer interview synthesis

**Not for:**
- Live in-call assistance
- Teams not on Fireflies
- Writing back into Fireflies

## Recipes

### Pull every customer call where pricing came up

```
Using the Fireflies connector, find every customer call from the last 30 days where pricing or budget came up. For each, give me the meeting title, the date, and a two-sentence summary of the pricing discussion.
```

_Tested with: Claude Desktop, Cursor_

## Description

Fireflies.ai is the most widely deployed AI meeting recorder, and its official remote MCP at `https://api.fireflies.ai/mcp` exposes the same corpus to Claude, Cursor, and any MCP-compatible client. Use OAuth via the Claude Connector listing for the one-click path, or wire it up locally with `mcp-remote` and a Bearer API key from your Fireflies dashboard.

## Why it matters

Fireflies has the largest installed base of any AI notetaker — for many teams its corpus is the canonical record of every external and internal meeting. An MCP that exposes that corpus to Claude/Cursor closes the loop between "the meeting happened" and "the agent can quote it".

## Key features

- Official remote MCP at `https://api.fireflies.ai/mcp`
- Listed in the Claude Connector directory (OAuth, one-click)
- API-key option via `mcp-remote` for self-managed clients
- Search across the full transcript corpus
- Returns AI summaries, action items, and topic timestamps

## FAQ

### OAuth or API key — which should I use?

OAuth via the Claude Connector listing is the cleanest path for Claude users — no key to rotate and revocation lives in Fireflies. For Cursor, custom clients, or scripted flows where you want a long-lived credential, use the API key from fireflies.ai/dashboard/settings/api with the `mcp-remote` wrapper.

### How does it compare to Fellow and Fathom?

All three are first-party remote MCPs that expose the same shape of data (transcripts, summaries, action items). Pick based on which notetaker your team already uses — none of them ingest meetings recorded by a competitor. Fellow is the only one currently flagged as Anthropic-verified.

### What is the API rate limit?

Fireflies enforces standard API rate limits per workspace. Tight agent loops that fan out queries can hit them; cache results when summarizing large date ranges.

### Can it transcribe live, or only past meetings?

Past meetings only via the MCP. Recording happens in Fireflies itself (calendar bot or browser extension); the MCP queries the resulting transcripts after the call ends.

## Changelog

- **2026-06-11** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-10-01** — Initial directory listing.