Fireflies MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIREFLIES_API_KEY | Yes | Your Fireflies API key from https://fireflies.ai/dashboard/settings/api |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| 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. |
| 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. |
| fireflies_generate_summaryB | Generate a summary of a meeting transcript |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
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.
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.
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.
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.