home / mcp / fireflies mcp server

Fireflies MCP Server

An MCP server for fireflies

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "props-labs-fireflies-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@props-labs/mcp/fireflies"
      ],
      "env": {
        "FIREFLIES_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}

You can run the Fireflies MCP Server locally to retrieve, search, and summarize meeting transcripts from the Fireflies.ai API. This MCP server exposes endpoints via a small local process and lets you connect your MCP client to fetch transcripts, get details, search content, and generate summaries.

How to use

You interact with the Fireflies MCP Server through an MCP client by starting the server with your API key and then issuing calls to the four available tools. The server handles authentication with Fireflies, retrieves transcript data, and can produce concise summaries in different formats. Use the transcript listing tool to browse transcripts, fetch detailed information for a specific transcript, perform keyword searches across transcripts, and generate formatted summaries at will.

How to install

Prerequisites you need before installation: a current Node.js environment and npm or pnpm as your package manager.

1) Clone the project repository and navigate into its directory.

2) Install dependencies.

npm install
# or
pnpm install

3) Build the project.

npm run build
# or
pnpm build

4) Configure your environment and start the server using your API key. You will set FIREFLIES_API_KEY to your Fireflies API key before starting.

FIREFLIES_API_KEY=your_api_key npm start
# or
FIREFLIES_API_KEY=your_api_key pnpm start

If you prefer a setup script, you can run the setup flow and then start the server with the API key.

./setup.sh
FIREFLIES_API_KEY=your_api_key npm start

Configuration and how to connect your client

To use this MCP server with your Claude Desktop or any MCP client, configure the MCP connection to run the server as a local stdio process using the following setup.

{
  "mcpServers": {
    "fireflies": {
      "command": "npx",
      "args": [
        "-y",
        "@props-labs/mcp/fireflies"
      ],
      "env": {
        "FIREFLIES_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}

Notes on tools and usage

The MCP server provides four tools you can call from your MCP client. Each tool focuses on a specific capability: listing transcripts, retrieving detailed transcript information, searching transcripts by query, and generating a formatted summary.

Security and secrets

Treat your API key as a secret. Do not commit FIREFLIES_API_KEY into source control. Use environment variables to inject the key at runtime and consider using a secret store or runtime vault in production environments.

Troubleshooting and tips

If you encounter authentication errors, verify that FIREFLIES_API_KEY is correctly set in your shell before starting the server. Ensure your API key has the required permissions for transcript retrieval, detail retrieval, searching, and summary generation.

Available tools

fireflies_get_transcripts

Retrieve a list of meeting transcripts with optional filtering. Inputs include limit, from_date, and to_date. Returns an array of transcript objects with basic information.

fireflies_get_transcript_details

Get detailed information about a specific transcript. Inputs include transcript_id. Returns comprehensive transcript details including speakers, content, and metadata.

fireflies_search_transcripts

Search for transcripts containing specific keywords. Inputs include query and limit. Returns an array of matching transcript objects.

fireflies_generate_summary

Generate a summary of a meeting transcript. Inputs include transcript_id and an optional format (bullet_points or paragraph). Returns the generated summary text.