Skip to main content
Glama
Fireflies MCP Server

Fireflies MCP Server

by cassler

Fireflies MCP Server

npm version MIT License PRs Welcome

Supercharge your meeting workflows with seamless transcript access, search, and AI-powered summariesβ€”right from your terminal or automation tools!


πŸš€ Introduction

Fireflies MCP Server is an open source Modern Command Protocol (MCP) server that unlocks the full power of the Fireflies.ai API. Instantly retrieve, search, and summarize your meeting transcripts with simple commands or integrate into your favorite tools. Perfect for productivity enthusiasts, automation fans, and teams who want to get more from their meeting data.


Related MCP server: Fathom MCP Server

✨ Why Fireflies MCP Server?

  • Instant Access: Fetch and filter all your Fireflies meeting transcripts in seconds.

  • Deep Insights: Get detailed transcript info, including speakers and full content.

  • Smart Search: Find exactly what you need with powerful keyword and phrase search.

  • AI Summaries: Generate concise, actionable summaries in your preferred format.

  • Easy Integration: Works with Claude Desktop, scripts, and any MCP-compatible client.

  • Open Source & Extensible: Community-driven, MIT-licensed, and ready for your contributions!


⚑️ Quick Start

# 1. Install (requires Node.js and npm or pnpm)
npm install -g fireflies-mcp-server

# 2. Get your Fireflies API key from https://fireflies.ai/dashboard/settings/api

# 3. Start the server
FIREFLIES_API_KEY=your_api_key fireflies-mcp-server

πŸ›  Features

  • Transcript Management: List and filter your Fireflies meeting transcripts

  • Transcript Details: Retrieve in-depth information for any transcript, including speakers and full content

  • Keyword Search: Locate transcripts by searching for specific words or phrases

  • Automated Summaries: Instantly generate concise summaries in either paragraph or bullet point format


πŸ”Œ Endpoints

  • fireflies_get_transcripts β€” List transcripts (with optional filters: limit, from_date, to_date)

  • fireflies_get_transcript_details β€” Get full details for a transcript (transcript_id)

  • fireflies_search_transcripts β€” Search transcripts by keyword or phrase (query, optional limit)

  • fireflies_generate_summary β€” Generate a summary for a transcript (transcript_id, optional format)


πŸ§‘β€πŸ’» Setup & Usage

1. Prerequisites

2. Installation

npm install
# or
pnpm install

3. Build

npm run build
# or
pnpm build

4. (Optional) Use a Custom Build Directory

By default, the build output goes to the dist directory. To specify a different build/output directory, set the BUILD_DIR environment variable before building:

BUILD_DIR=custom-dist npm run build

This will output the build to custom-dist instead of dist.

5. Configuration for Claude Desktop

After building, you'll want to point Claude Desktop to your custom build directory. Here's what your terminal output and configuration might look like:

$ echo "Add this to your claude_desktop_config.json mcpServers array:"
Add this to your claude_desktop_config.json mcpServers array:

{
  "mcpServers": {
    "fireflies": {
      "command": "node",
      "args": ["/absolute/path/to/custom-dist/index.js"],
      "env": {
        "FIREFLIES_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}

Replace /absolute/path/to/custom-dist/index.js with the actual path to your custom build output.

6. Running the Server

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

Or use the setup script:

./setup.sh
FIREFLIES_API_KEY=your_api_key npm start

🀝 Contributing

We love contributions! Whether it's a bug fix, new feature, or documentation improvement, your help is welcome. Please check out CONTRIBUTING.md for guidelines, or open an issue to start a discussion.


πŸ’¬ Community & Support


πŸ“„ License

This project is licensed under the MIT License. See the LICENSE file for details.

Available Tools

4 tools
fireflies_generate_summaryB

Generate a summary of a meeting transcript

Inputs: transcript_id (required), format.

fireflies_get_transcript_detailsB

Retrieve detailed information about a specific transcript. Returns a human-readable formatted transcript with speaker names and text, along with metadata and summary information.

Inputs: transcript_id (required).

fireflies_get_transcriptsA

Retrieve a list of meeting transcripts with optional filtering. By default, returns up to 20 most recent transcripts with no date filtering. Note that this operation may take longer for large datasets and might timeout. If a timeout occurs, a minimal set of transcript data will be returned.

Inputs: limit, from_date, to_date.

fireflies_search_transcriptsC

Search for transcripts containing specific keywords, with optional date filtering. Returns a human-readable list of matching transcripts with metadata and summary information.

Inputs: query (required), limit, from_date, to_date.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: generate_summary creates a summary, get_transcript_details retrieves a single transcript with details, get_transcripts lists transcripts, and search_transcripts finds transcripts by keywords. There is no overlap in functionality, making it easy for an agent to select the correct tool.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with the prefix 'fireflies_' (e.g., fireflies_generate_summary, fireflies_get_transcript_details). The verbs (generate, get, search) are clear and appropriately matched to their actions, ensuring predictability and readability.

    Tool Count5/5

    With 4 tools, the server is well-scoped for handling meeting transcripts, covering key operations: listing, retrieving details, searching, and generating summaries. This count is appropriate as each tool earns its place without being too sparse or overwhelming.

    Completeness4/5

    The tool set provides strong coverage for the domain of meeting transcript management, including listing, detailed retrieval, searching, and summary generation. A minor gap is the lack of update or delete operations, but these might not be necessary for a read-focused transcript service, and agents can work around this limitation.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to access Fathom AI meeting data including transcripts, summaries, teams, and team members. Provides tools to list meetings with filters, retrieve detailed transcripts and summaries, and manage team information.
      16 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides access to Fathom meeting recordings, enabling users to list meetings with filters, retrieve AI-generated summaries, and access full transcripts with speaker attribution and timestamps.
      3
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to search and retrieve meeting transcripts from Otter.ai, supporting full-text search, speaker identification, and transcript retrieval.
      5
      MIT