Skip to main content
Book a demo

Fireflies

Meeting intelligence with transcript analysis and conversation insights

Book a demo View documentation

Tools

8 available tools

Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.

8 tools found.

  • Get meeting details

    Read only

    Tool name: fireflies_get_transcript

    Fetches detailed meeting transcript by ID, with optional field filtering.

  • Get meeting summary

    Read only

    Tool name: fireflies_get_summary

    Fetches meeting summary by ID, with optional field filtering.

  • Search meetings

    Read only

    Tool name: fireflies_get_transcripts

    Queries multiple meeting transcripts using filter properties (date, keyword, email, etc.).

  • Get user details

    Read only

    Tool name: fireflies_get_user

    Fetches user account details.

  • Get user groups

    Read only

    Tool name: fireflies_get_usergroups

    Fetches user groups for the authenticated user or their team.

  • Get user contacts

    Read only

    Tool name: fireflies_get_user_contacts

    Fetches contact list for the authenticated user.

  • Search meeting transcripts

    Read only

    Tool name: fireflies_search

    Advanced search for meeting transcripts using a mini grammar.

  • Fetch meeting details

    Read only

    Tool name: fireflies_fetch

    Retrieve complete meeting transcript with full conversation, metadata, and insights for a specific meeting ID.

Compatibility

Connect Fireflies to the clients your teams already use

27 AI clients can connect to Fireflies through Runlayer. Pick one for its setup steps and controls.

CursorVS CodeClaudeClaude CodeClaude CoworkChatGPTWindsurfGooseCodexHermesGumloopRaycastWarpGitHub CopilotGitHub Copilot CLIMicrosoft 365 CopilotGemini CLIZedCline CLIAntigravityOpenCodeCrushGleanLovablePerplexityECAOh My Pi

Why Runlayer

Why connect Fireflies through Runlayer?

One approved path

Approve Fireflies once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.

Fine-grained policy

Control who can use each server, tool, and resource, and under which runtime conditions.

Runtime security

Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.

Audit and observability

Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.

Frequently asked questions