# Fireflies — how to use (mcp.ai)

Fireflies in natural language: access meeting transcripts, summaries, action items, participants and bites. You connect with your own Fireflies API key, generated in your account settings. Multiple Fireflies accounts can be connected to the same MCP.

## Option A — via MCP (recommended)
Remote MCP endpoint (HTTP, streamable): `https://api.mcp.ai/p_fireflies?ms=1781044440000`
Add it as a custom/remote MCP connector in your client (Claude, Cursor, VS Code…), then authenticate when prompted. Once connected, ask the agent to use the server's tools (e.g. `fireflies_add_to_live`).

## Option B — via direct REST API
Base URL: `https://api.mcp.ai/api/fireflies`
Auth: `Authorization: Bearer sk_live_…` — create a workspace API key at https://mcp.ai/settings/api-keys
Discover endpoints: `GET https://api.mcp.ai/api/fireflies/_endpoints`

### Endpoints
- `POST https://api.mcp.ai/api/fireflies/add/to/live` — The addtolive action allows you to add the fireflies.ai bot to an ongoing meeting. note: this action requires a paid fireflies plan to add bots to meetings.
  - body: { title?: string, duration?: integer, language?: string, attendees?: object[], meeting_link: string, meeting_password?: string }
- `POST https://api.mcp.ai/api/fireflies/delete/transcript/by/id` — The deletetranscriptbyid action is designed to delete a specific transcript by its id.
  - body: { id?: string }
- `POST https://api.mcp.ai/api/fireflies/fetch/ai/app/outputs` — Fetch outputs for a specific ai app or meeting/transcript.
  - body: { skip?: integer, limit?: integer, app_id: string, transcript_id: string }
- `POST https://api.mcp.ai/api/fireflies/get/bite/by/id` — The getbite action is designed to fetch details associated with a specific bite id.
  - body: { id?: string }
- `POST https://api.mcp.ai/api/fireflies/get/bites` — The getbites action is designed to fetch a list of bites against input arguments.
  - body: { mine?: boolean, skip?: integer, limit?: integer, my_team?: boolean, transcript_id?: string }
- `POST https://api.mcp.ai/api/fireflies/get/transcript/by/id` — The gettranscriptbyid action is designed to fetch details associated with a specific transcript id. note: this action requires a paid fireflies plan to access transcript details.
  - body: { id: string }
- `POST https://api.mcp.ai/api/fireflies/get/transcripts` — The gettranscripts action is designed to fetch a list of transcripts against input arguments.
  - body: { skip?: integer, limit?: integer, title?: string, to_date?: string, user_id?: string, from_date?: string, host_email?: string, organizer_email?: string, participant_email?: string }
- `POST https://api.mcp.ai/api/fireflies/get/user/by/id` — The getuser action is designed to fetch details associated with a specific user id.
  - body: { id: string }
- `POST https://api.mcp.ai/api/fireflies/get/users` — The getusers action is designed to fetch a list of all users within the team.
- `POST https://api.mcp.ai/api/fireflies/upload/audio` — The uploadaudio action allows you to upload audio files to fireflies.ai for transcription. note: this action requires a paid fireflies plan to upload and transcribe audio files.
  - body: { url: string, title: string, webhook?: string, attendees?: object[], save_video?: boolean, custom_language?: string, client_reference_id?: string }

## Example prompts
- "List my transcribed meetings from last week and the main action items"
- "Summarize the transcript of my last meeting"
- "What were the decisions and tasks agreed in the project meeting?"

## More
- Page: https://mcp.ai/fireflies
- Agent spec (llms.txt): https://mcp.ai/fireflies/llms.txt
- Postman collection: https://mcp.ai/fireflies/postman.json