Fireflies MCP Server for Claude

Content

Unlock the power of your meeting data by connecting Claude to Fireflies.ai's meeting intelligence platform. Automatically extract action items, search conversation history, analyze speaker participation, and generate comprehensive meeting summaries through natural language commands, transforming how you capture and act on meeting insights.

Features

• Access meeting transcripts and recordings
• Retrieve automated meeting summaries
• Search conversation content
• Extract action items and decisions
• Analyze speaker analytics and participation
• Advanced Fireflies meeting transcription and analysis with AI-powered insights, action item extraction, and meeting summary generation
• Batch operations support for efficient bulk meeting processing, transcript analysis, and data export with automatic rate limit handling and retry logic
• Real-time meeting synchronization capabilities with webhook integration support for monitoring new meetings and triggering automated workflows

Use Cases

• Review meeting outcomes and decisions
• Extract action items for follow-up
• Search past discussions by topic
• Generate meeting reports for stakeholders
• Track speaker participation metrics
• Build automated meeting management workflows that sync external systems with Fireflies for real-time meeting transcription and analysis

Installation

Claude Code

1. claude mcp add --transport http fireflies https://api.fireflies.ai/mcp
2. Add your Fireflies API key to the configuration (Authorization header with Bearer token)
3. Verify installation: claude mcp list
4. Test connection: claude mcp status fireflies

Claude Desktop

1. Open your Claude Desktop configuration file (see configPath below)
2. Add the Fireflies server configuration with HTTP transport and your API key
3. Restart Claude Desktop
4. Authenticate with your Fireflies account (API key should be in Authorization header)

Requirements

• Fireflies.ai account (sign up at https://fireflies.ai if needed)
• Fireflies API key (obtain from Fireflies settings/API section)
• OAuth authentication support (for workspace access)
• HTTP transport support (remote MCP server at https://api.fireflies.ai/mcp)
• Claude Desktop 0.7.0+ or Claude Code with MCP support
• Internet connection (remote API access required)
• Understanding of rate limits (Free/Pro: 50 requests/day, Business/Enterprise: 60 requests/minute)
• Workspace permissions (viewer or higher role for accessing meetings in Fireflies workspace)
• Understanding of meeting privacy settings (meetings must allow API access)
• Understanding of Fireflies workspace structure and meeting organization

Configuration

{
  "fireflies": {
    "url": "https://api.fireflies.ai/mcp",
    "transport": "http"
  }
}

Examples

Get action items from today's standup

Common usage pattern for this MCP server

Ask Claude: "Get action items from today's standup"

Search for discussions about Q4 planning

Common usage pattern for this MCP server

Ask Claude: "Search for discussions about Q4 planning"

Generate summary of customer call

Common usage pattern for this MCP server

Ask Claude: "Generate summary of customer call"

Find all mentions of budget in recent meetings

Common usage pattern for this MCP server

Ask Claude: "Find all mentions of budget in recent meetings"

Get Meeting Transcript

Retrieve a meeting transcript with speaker identification

// Get Fireflies meeting transcript
const transcript = await fireflies.transcripts.get({
  meeting_id: "meeting-id",
  format: "text",
  include_speakers: true,
});

Security

• OAuth authentication for workspace access
• Respect meeting privacy settings
• Control transcript access permissions
• Regular data audits recommended
• Fireflies API keys and access tokens must be securely stored and never exposed in client-side code or public repositories - use environment variables and secure credential management
• Fireflies OAuth access tokens should be used for third-party integrations to ensure proper access control, token lifecycle management, and automatic token refresh
• Fireflies meeting IDs and transcript data may contain sensitive business information and personal conversations - ensure Fireflies resource identifiers are kept private and not shared in public configurations
• Rate limiting and API quota management are critical for Fireflies MCP servers - implement proper rate limit handling, retry logic, and quota monitoring to prevent service disruption
• Fireflies webhook configurations and payloads may contain sensitive meeting transcripts and participant information - ensure webhook endpoints are properly secured with authentication and HTTPS encryption

Troubleshooting

Too many requests error with code 429

Free/Pro plans: 50 requests/day limit. Business/Enterprise: 60 requests/minute. Check retryAfter timestamp in error response. Wait specified time before retry or upgrade plan for higher limits.

Invalid API key or authentication failed error

Add Authorization header with Bearer YOUR_API_KEY format. Verify API key hasn't expired in Fireflies settings. Check for typos and regenerate key if authentication continues to fail.

Cannot access meeting transcripts or recordings

Verify workspace permissions grant access to meetings. Check meeting privacy settings allow API access. Ensure your account has viewer or higher role for target meetings in Fireflies workspace.

Transcripts incomplete or missing sections

Check audio quality of original recording. Verify storage limits haven't been exceeded for your plan tier. Review transcript settings for language and accuracy preferences in Fireflies workspace.

Fireflies MCP server authentication errors with API keys

Verify API key is valid and not expired. Check API key permissions match required operations. Ensure API key format is correct (Bearer token in Authorization header). For OAuth integrations, verify token refresh logic is working correctly.

Fireflies rate limit errors when processing multiple meetings

Implement exponential backoff retry logic with jitter. Use Fireflies API rate limit headers to monitor usage. Reduce concurrent requests. Cache frequently accessed meeting data. Fireflies allows 100 requests per minute per API key.

Fireflies meeting or transcript access denied errors

Verify API key has access to the meeting. Check meeting permissions and account membership. Ensure API key has required permissions (read transcripts, read meetings) for target operations.

Fireflies MCP server connection timeouts or network errors

Check network connectivity and firewall settings. Verify Fireflies API endpoints are accessible. Increase request timeout values. Implement connection pooling and retry mechanisms with exponential backoff.