# How to integrate Fireflies MCP with Claude Code

```json
{
  "title": "How to integrate Fireflies MCP with Claude Code",
  "toolkit": "Fireflies",
  "toolkit_slug": "fireflies",
  "framework": "Claude Code",
  "framework_slug": "claude-code",
  "url": "https://composio.dev/toolkits/fireflies/framework/claude-code",
  "markdown_url": "https://composio.dev/toolkits/fireflies/framework/claude-code.md",
  "updated_at": "2026-05-12T10:11:43.106Z"
}
```

## Introduction

Manage your Fireflies directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.
You can do this in two different ways:
- Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach
- Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control

## Also integrate Fireflies with

- [ChatGPT](https://composio.dev/toolkits/fireflies/framework/chatgpt)
- [OpenAI Agents SDK](https://composio.dev/toolkits/fireflies/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/fireflies/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/fireflies/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/fireflies/framework/codex)
- [Cursor](https://composio.dev/toolkits/fireflies/framework/cursor)
- [VS Code](https://composio.dev/toolkits/fireflies/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/fireflies/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/fireflies/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/fireflies/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/fireflies/framework/cli)
- [Google ADK](https://composio.dev/toolkits/fireflies/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/fireflies/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/fireflies/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/fireflies/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/fireflies/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/fireflies/framework/crew-ai)

## TL;DR

- Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
- Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
- Handling Large tool responses out of LLM context to minimize context rot.
- Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

## Connect Fireflies to Claude Code

### Connecting Fireflies to Claude Code using Composio
1. Add the Composio MCP to Claude

```bash
claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp
```

## What is Claude Code?

Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working.
Key features include:
- Terminal-Native Experience: Work with Claude directly in your command line without switching contexts
- MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities
- Project Context: Claude understands your project structure and can read, write, and modify files
- Interactive Development: Ask questions, debug code, and get help in real-time while coding
- Multi-Platform: Works on macOS, Linux, WSL, and Windows

## What is the Fireflies MCP server, and what's possible with it?

The Fireflies MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Fireflies account. It provides structured and secure access to your voice conversations, so your agent can perform actions like transcribing meetings, summarizing discussions, searching transcripts, and managing audio files on your behalf.
- Automated meeting transcription: Instantly upload audio files or add the Fireflies bot to live meetings so your agent can generate accurate transcripts for later review.
- AI-powered conversation summarization: Let your agent fetch concise, actionable summaries of calls and meetings to help you quickly catch up or share insights with your team.
- Transcript search and retrieval: Ask your agent to find specific transcripts or extract key segments from past conversations using keywords, dates, or participant names.
- Audio file management: Effortlessly upload, organize, or delete audio files and transcripts right from your agent, keeping your conversation library up to date.
- User and team insights: Enable your agent to fetch user details or team-wide meeting data, so you can stay on top of collaboration and engagement.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `FIREFLIES_ADD_TO_LIVE` | Add to Live Meeting | 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. |
| `FIREFLIES_CONTINUE_ASK_FRED_THREAD` | Continue AskFred Thread | Tool to continue an existing AskFred conversation thread with follow-up questions. This action CANNOT create new threads - it only works with existing thread IDs. Use when you need to maintain context from previous exchanges and ask additional questions about meeting data in the same conversation. To start a new thread, use FIREFLIES_CREATE_ASK_FRED_THREAD instead. |
| `FIREFLIES_CREATE_ASK_FRED_THREAD` | Create AskFred Thread | Tool to start a new AskFred conversation thread with a question about meetings. Use when you need to query meeting transcripts using natural language, either for a specific meeting or across multiple meetings with filters. Supports time-based queries and participant-focused queries. |
| `FIREFLIES_CREATE_BITE` | Create Bite | Tool to create a bite (short video or audio clip) from a transcript segment. Use when you need to extract a specific portion of a meeting recording with defined start and end times. |
| `FIREFLIES_DELETE_TRANSCRIPT_BY_ID` | Delete Transcript by ID | Permanently delete a transcript from the Fireflies account by its unique ID. This is a destructive action that cannot be undone. The transcript, along with its associated audio/video files and summaries, will be permanently removed. Rate limited to 10 requests per minute across all user tiers. Verify the target transcript via FIREFLIES_GET_TRANSCRIPTS and obtain explicit user confirmation before calling this tool. |
| `FIREFLIES_FETCH_AI_APP_OUTPUTS` | Fetch AI App Outputs | Tool to fetch AI App outputs for specific apps or transcripts. Use when you need to retrieve AI-generated results from Fireflies AI Apps for meetings. |
| `FIREFLIES_GET_ASK_FRED_THREAD` | Get AskFred Thread | Tool to get a specific AskFred conversation thread with full history. Use when retrieving a particular AskFred thread along with all its messages and conversation details. |
| `FIREFLIES_GET_ASK_FRED_THREADS` | Get AskFred Threads | Tool to retrieve a summary of all AskFred conversation threads for the current user. Use when you need to browse or list available AskFred conversations without fetching full message history. |
| `FIREFLIES_GET_BITE_BY_ID` | Get Bite by ID | Fetches details for a specific bite by ID. Requires a Fireflies plan that supports Bites and appropriate API scope. If the bite is not found, use FIREFLIES_GET_TRANSCRIPT_BY_ID to retrieve full transcript context instead. |
| `FIREFLIES_GET_BITES` | Get Transcripts | Fetches a list of bites (highlights) against input arguments. Bites are generated asynchronously after transcript completion — only call this after FIREFLIES_GET_TRANSCRIPT_BY_ID reports `status=completed`. Empty results are possible for valid meetings; use FIREFLIES_GET_TRANSCRIPT_BY_ID for full transcript context when bites are unavailable. |
| `FIREFLIES_GET_TRANSCRIPT_BY_ID` | Get Transcript by ID | Fetches details for a specific Fireflies transcript ID. Requires a paid Fireflies plan. Response is nested at data.outputs.data.transcript; fields like sentences and attendees can be null — handle gracefully. transcript.summary.action_items may be a single newline-delimited string rather than an array — split by line breaks instead of iterating as an array. Limit concurrent calls to ~3 and apply exponential backoff on 429 responses, respecting Retry-After headers. |
| `FIREFLIES_GET_TRANSCRIPTS` | Get Transcripts | Fetches a list of transcripts against input filters. Metadata filters (title, host_email, organizers, participants) match transcript metadata only, not spoken content. Pagination via skip/limit may trigger HTTP 429 on rapid requests; use backoff between pages. |
| `FIREFLIES_GET_USER_BY_ID` | Get User by ID | The GetUser Action is designed to fetch details associated with a specific user id. |
| `FIREFLIES_GET_USER_GROUPS` | Get User Groups | Tool to fetch a list of all user groups within the team with information about user groups including their members. Use when you need to retrieve team user groups, optionally filtering to only groups the current user belongs to with the mine parameter. |
| `FIREFLIES_GET_USERS` | Get Users | Fetches a list of all users within the team, including their full email addresses. Use to resolve complete email addresses from user names before passing to tools that require exact email addresses (no partial addresses or domain-only values). |
| `FIREFLIES_GRAPHQL_QUERY` | Execute GraphQL Query | Execute an authenticated, read-only Fireflies GraphQL operation (query) and return the full raw GraphQL response (data+errors) for reliable fallback and debugging. Use when higher-level tools fail due to schema mismatches or to access raw error details. |
| `FIREFLIES_SET_USER_ROLE` | Set User Role | Tool to update a user's role within a team. Use when you need to grant or revoke admin privileges. Only team administrators can execute this action. Teams must maintain at least one admin member at all times. |
| `FIREFLIES_UPDATE_MEETING_CHANNEL` | Update Meeting Channel | Tool to batch update channel assignments for 1-5 meeting transcripts. Use when you need to assign meetings to a specific channel. Requires meeting owner or team admin privileges. All-or-nothing semantics: if any transcript fails validation, none are updated. |
| `FIREFLIES_UPDATE_MEETING_PRIVACY` | Update Meeting Privacy | Tool to update the privacy setting of a meeting transcript. Use when you need to change meeting access permissions. Only meeting owners and team admins can update privacy settings. |
| `FIREFLIES_UPDATE_MEETING_TITLE` | Update Meeting Title | Tool to update the title of a meeting transcript. Use when you need to rename a meeting. Requires admin privileges and the meeting owner must be in your team. |
| `FIREFLIES_UPLOAD_AUDIO` | Upload Audio | The UploadAudio Action allows you to upload audio files to Fireflies.ai for transcription. Transcription is asynchronous — after submission, results may take several minutes to become available; use transcript retrieval tools to poll for completion. Note: This action requires a paid Fireflies plan to upload and transcribe audio files. |

## Supported Triggers

| Trigger slug | Name | Description |
|---|---|---|
| `FIREFLIES_TRANSCRIPTION_COMPLETE` | Transcription Complete Trigger | Triggers when a transcription is complete. Polls Fireflies API for transcripts created or updated since the last poll time. Handles rate limiting gracefully. |

## Creating MCP Server - Stand-alone vs Composio SDK

The Fireflies MCP server is an implementation of the Model Context Protocol that connects Claude Code (and other AI assistants like Claude and Cursor) directly to your Fireflies account. It provides structured and secure access so Claude can perform Fireflies operations on your behalf.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Claude Pro, Max, or API billing enabled Anthropic account
- Composio API Key
- A Fireflies account
- Basic knowledge of Python or TypeScript

### 1. Install Claude Code

To install Claude Code, use one of the following methods based on your operating system:
```bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd
```

### 2. Set up Claude Code

Open a terminal, go to your project folder, and start Claude Code:
- Claude Code will open in your terminal
- Follow the prompts to sign in with your Anthropic account
- Complete the authentication flow
- Once authenticated, you can start using Claude Code
```bash
cd your-project-folder
claude
```

### 3. Set up environment variables

Create a .env file in your project root with the following variables:
- COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code))
- USER_ID identifies the user for session management (use any unique identifier)
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
```

### 4. Install Composio library

No description provided.
```python
pip install composio-core python-dotenv
```

```typescript
npm install @composio/core dotenv
```

### 5. Generate Composio MCP URL

No description provided.
```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["fireflies"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http fireflies-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['fireflies'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http fireflies-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

### 6. Run the script and copy the MCP URL

No description provided.
```python
python generate_mcp_url.py
```

```typescript
node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts
```

### 7. Add Fireflies MCP to Claude Code

In your terminal, add the MCP server using the command from the previous step. The command format is:
- claude mcp add registers a new MCP server with Claude Code
- --transport http specifies that this is an HTTP-based MCP server
- The server name (fireflies-composio) is how you'll reference it
- The URL points to your Composio Tool Router session
- --headers includes your Composio API key for authentication
After running the command, close the current Claude Code session and start a new one for the changes to take effect.
```bash
claude mcp add --transport http fireflies-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude
```

### 8. Verify the installation

Check that your Fireflies MCP server is properly configured.
- This command lists all MCP servers registered with Claude Code
- You should see your fireflies-composio entry in the list
- This confirms that Claude Code can now access Fireflies tools
If everything is wired up, you should see your fireflies-composio entry listed:
```bash
claude mcp list
```

### 9. Authenticate Fireflies

The first time you try to use Fireflies tools, you'll be prompted to authenticate.
- Claude Code will detect that you need to authenticate with Fireflies
- It will show you an authentication link
- Open the link in your browser (or copy/paste it)
- Complete the Fireflies authorization flow
- Return to the terminal and start using Fireflies through Claude Code
Once authenticated, you can ask Claude Code to perform Fireflies operations in natural language. For example:
- "Transcribe this uploaded meeting audio file"
- "Summarize my last five recorded calls"
- "List all transcripts involving the marketing team"

## Complete Code

```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["fireflies"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http fireflies-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['fireflies'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http fireflies-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

## Conclusion

You've successfully integrated Fireflies with Claude Code using Composio's MCP server. Now you can interact with Fireflies directly from your terminal using natural language commands.
Key features of this setup:
- Terminal-native experience without switching contexts
- Natural language commands for Fireflies operations
- Secure authentication through Composio's managed MCP
- Tool Router for dynamic tool discovery and execution
Next steps:
- Try asking Claude Code to perform various Fireflies operations
- Add more toolkits to your Tool Router session for multi-app workflows
- Integrate this setup into your development workflow for increased productivity
You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

## How to build Fireflies MCP Agent with another framework

- [ChatGPT](https://composio.dev/toolkits/fireflies/framework/chatgpt)
- [OpenAI Agents SDK](https://composio.dev/toolkits/fireflies/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/fireflies/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/fireflies/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/fireflies/framework/codex)
- [Cursor](https://composio.dev/toolkits/fireflies/framework/cursor)
- [VS Code](https://composio.dev/toolkits/fireflies/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/fireflies/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/fireflies/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/fireflies/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/fireflies/framework/cli)
- [Google ADK](https://composio.dev/toolkits/fireflies/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/fireflies/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/fireflies/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/fireflies/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/fireflies/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/fireflies/framework/crew-ai)

## Related Toolkits

- [Firecrawl](https://composio.dev/toolkits/firecrawl) - Firecrawl automates large-scale web crawling and data extraction. It helps organizations efficiently gather, index, and analyze content from online sources.
- [Tavily](https://composio.dev/toolkits/tavily) - Tavily offers powerful search and data retrieval from documents, databases, and the web. It helps teams locate and filter information instantly, saving hours on research.
- [Exa](https://composio.dev/toolkits/exa) - Exa is a data extraction and search platform for gathering and analyzing information from websites, APIs, or databases. It helps teams quickly surface insights and automate data-driven workflows.
- [Serpapi](https://composio.dev/toolkits/serpapi) - SerpApi is a real-time API for structured search engine results. It lets you automate SERP data collection, parsing, and analysis for SEO and research.
- [Peopledatalabs](https://composio.dev/toolkits/peopledatalabs) - Peopledatalabs delivers B2B data enrichment and identity resolution APIs. Supercharge your apps with accurate, up-to-date business and contact data.
- [Snowflake](https://composio.dev/toolkits/snowflake) - Snowflake is a cloud data warehouse built for elastic scaling, secure data sharing, and fast SQL analytics across major clouds.
- [Posthog](https://composio.dev/toolkits/posthog) - PostHog is an open-source analytics platform for tracking user interactions and product metrics. It helps teams refine features, analyze funnels, and reduce churn with actionable insights.
- [Amplitude](https://composio.dev/toolkits/amplitude) - Amplitude is a digital analytics platform for product and behavioral data insights. It helps teams analyze user journeys and make data-driven decisions quickly.
- [Bright Data MCP](https://composio.dev/toolkits/brightdata_mcp) - Bright Data MCP is an AI-powered web scraping and data collection platform. Instantly access public web data in real time with advanced scraping tools.
- [Browseai](https://composio.dev/toolkits/browseai) - Browseai is a web automation and data extraction platform that turns any website into an API. It's perfect for monitoring websites and retrieving structured data without manual scraping.
- [ClickHouse](https://composio.dev/toolkits/clickhouse) - ClickHouse is an open-source, column-oriented database for real-time analytics and big data processing using SQL. Its lightning-fast query performance makes it ideal for handling large datasets and delivering instant insights.
- [Coinmarketcal](https://composio.dev/toolkits/coinmarketcal) - CoinMarketCal is a community-powered crypto calendar for upcoming events, announcements, and releases. It helps traders track market-moving developments and stay ahead in the crypto space.
- [Control d](https://composio.dev/toolkits/control_d) - Control d is a customizable DNS filtering and traffic redirection platform. It helps you manage internet access, enforce policies, and monitor usage across devices and networks.
- [Databox](https://composio.dev/toolkits/databox) - Databox is a business analytics platform that connects your data from any tool and device. It helps you track KPIs, build dashboards, and discover actionable insights.
- [Databricks](https://composio.dev/toolkits/databricks) - Databricks is a unified analytics platform for big data and AI on the lakehouse architecture. It empowers data teams to collaborate, analyze, and build scalable solutions efficiently.
- [Datagma](https://composio.dev/toolkits/datagma) - Datagma delivers data intelligence and analytics for business growth and market discovery. Get actionable market insights and track competitors to inform your strategy.
- [Delighted](https://composio.dev/toolkits/delighted) - Delighted is a customer feedback platform based on the Net Promoter System®. It helps you quickly gather, track, and act on customer sentiment.
- [Dovetail](https://composio.dev/toolkits/dovetail) - Dovetail is a research analysis platform for transcript review and insight generation. It helps teams code interviews, analyze feedback, and create actionable research summaries.
- [Dub](https://composio.dev/toolkits/dub) - Dub is a short link management platform with analytics and API access. Use it to easily create, manage, and track branded short links for your business.
- [Elasticsearch](https://composio.dev/toolkits/elasticsearch) - Elasticsearch is a distributed, RESTful search and analytics engine for all types of data. It delivers fast, scalable search and powerful analytics across massive datasets.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Fireflies MCP?

With a standalone Fireflies MCP server, the agents and LLMs can only access a fixed set of Fireflies tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Fireflies and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Claude Code?

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Fireflies tools.

### Can I manage the permissions and scopes for Fireflies while using Tool Router?

Yes, absolutely. You can configure which Fireflies scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Fireflies data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)