# How to integrate Firecrawl MCP with Claude Agent SDK ```json { "title": "How to integrate Firecrawl MCP with Claude Agent SDK", "toolkit": "Firecrawl", "toolkit_slug": "firecrawl", "framework": "Claude Agent SDK", "framework_slug": "claude-agents-sdk", "url": "https://composio.dev/toolkits/firecrawl/framework/claude-agents-sdk", "markdown_url": "https://composio.dev/toolkits/firecrawl/framework/claude-agents-sdk.md", "updated_at": "2026-10-12T13:38:46.678Z" } ``` ## Introduction This guide walks you through connecting Firecrawl to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Firecrawl agent that can extract all product prices from this e-commerce site, crawl competitor blogs for latest article summaries, map all subpages linked from homepage url through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Firecrawl account through Composio's Firecrawl MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Firecrawl with - [Claude Code](https://composio.dev/toolkits/firecrawl/framework/claude-code) - [Cursor](https://composio.dev/toolkits/firecrawl/framework/cursor) - [ChatGPT](https://composio.dev/toolkits/firecrawl/framework/chatgpt) - [Claude Cowork](https://composio.dev/toolkits/firecrawl/framework/claude-cowork) - [Antigravity](https://composio.dev/toolkits/firecrawl/framework/antigravity) - [OpenAI Agents SDK](https://composio.dev/toolkits/firecrawl/framework/open-ai-agents-sdk) - [Grok Bot](https://composio.dev/toolkits/firecrawl/framework/grok-bot) - [Muse](https://composio.dev/toolkits/firecrawl/framework/muse) - [Codex](https://composio.dev/toolkits/firecrawl/framework/codex) - [Grok Build](https://composio.dev/toolkits/firecrawl/framework/grok-build) - [VS Code](https://composio.dev/toolkits/firecrawl/framework/vscode) - [OpenCode](https://composio.dev/toolkits/firecrawl/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/firecrawl/framework/openclaw) - [Hermes](https://composio.dev/toolkits/firecrawl/framework/hermes-agent) - [Atomic Agent](https://composio.dev/toolkits/firecrawl/framework/atomic-agent) - [Pi](https://composio.dev/toolkits/firecrawl/framework/pi-agent) - [DeepSeek Harness](https://composio.dev/toolkits/firecrawl/framework/deepseek) - [Google ADK](https://composio.dev/toolkits/firecrawl/framework/google-adk) - [LangChain](https://composio.dev/toolkits/firecrawl/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/firecrawl/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/firecrawl/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/firecrawl/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/firecrawl/framework/crew-ai) - [Pydantic AI](https://composio.dev/toolkits/firecrawl/framework/pydantic-ai) - [AutoGen](https://composio.dev/toolkits/firecrawl/framework/autogen) ## TL;DR Here's what you'll learn: - Get and set up your Claude/Anthropic and Composio API keys - Install the necessary dependencies - Initialize Composio and create a Tool Router session for Firecrawl - Configure an AI agent that can use Firecrawl as a tool - Run a live chat session where you can ask the agent to perform Firecrawl operations ## What is Claude Agent SDK? The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management. Key features include: - Native MCP Support: Built-in support for Model Context Protocol servers - Permission Modes: Control tool execution permissions - Streaming Responses: Real-time response streaming for interactive applications - Context Manager: Clean async context management for sessions ## What is the Firecrawl MCP server, and what's possible with it? The Firecrawl MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Firecrawl account. It provides structured and secure access to web crawling, site mapping, content extraction, and usage data, so your agent can scrape multiple pages, discover website URLs, run agentic extraction, monitor jobs, and manage active crawls on your behalf. - Batch website scraping: Have your agent scrape content from multiple URLs at once and check when the collected results are ready. - Website discovery and mapping: Direct your agent to find pages from a starting website, filter them with a search query, and control sitemap or subdomain coverage. - Agentic web extraction: Let the agent start multi-page extraction tasks that can navigate and interact with websites, then retrieve their results. - Crawl monitoring and control: Instruct your agent to check crawl progress, review completed results, or cancel an active or queued crawl. - Credit and token tracking: Have your agent report your team’s current Firecrawl credit usage, extraction token usage, and remaining balance. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `FIRECRAWL_AGENT_CANCEL` | Cancel an agent job | Tool to cancel an in-progress agent job by its ID. Use when you need to terminate an active agent operation. The API returns a success boolean upon cancellation. | | `FIRECRAWL_BATCH_SCRAPE` | Batch scrape multiple URLs | Tool to scrape multiple URLs in batch with concurrent processing. Use when you need to scrape multiple web pages efficiently with customizable formats and content filtering. | | `FIRECRAWL_BATCH_SCRAPE_CANCEL` | Cancel a batch scrape job | Tool to cancel a running batch scrape job using its unique identifier. Use when you need to terminate an in-progress batch scrape operation. | | `FIRECRAWL_BATCH_SCRAPE_GET` | Get batch scrape status | Retrieves the current status and results of a batch scrape job using the job ID. Use this to check batch scrape progress and retrieve scraped data. | | `FIRECRAWL_BATCH_SCRAPE_GET_ERRORS` | Get errors from batch scrape job | Tool to retrieve error details from a batch scrape job, including failed URLs and URLs blocked by robots.txt. Use when you need to debug or understand why certain pages failed to scrape in a batch operation. | | `FIRECRAWL_CRAWL` | Start a web crawl | Initiates a Firecrawl web crawl from a given URL, applying various filtering and content extraction rules, and polls until the job is complete; ensure the URL is accessible and any regex patterns for paths are valid. | | `FIRECRAWL_CRAWL_CANCEL` | Cancel a crawl job | Cancels an active or queued web crawl job using its ID; attempting to cancel completed, failed, or previously canceled jobs will not change their state. | | `FIRECRAWL_CRAWL_DELETE` | Cancel a crawl job | Tool to cancel a running crawl job by its ID. Use when you need to stop an active crawl operation. The API returns a status of 'cancelled' upon successful cancellation. | | `FIRECRAWL_CRAWL_GET` | Get crawl job status | Tool to retrieve the status and results of a Firecrawl crawl job. Use when you need to check the progress or get data from an ongoing or completed crawl operation. Returns crawl status, progress metrics, credits used, and the crawled page data. | | `FIRECRAWL_CRAWL_GET_ERRORS` | Get errors from a crawl job | Tool to retrieve errors from a Firecrawl crawl job. Use when you need to understand why certain pages failed to scrape or which URLs were blocked by robots.txt during a crawl operation. | | `FIRECRAWL_CRAWL_LIST_ACTIVE` | Get all active crawl jobs | Tool to retrieve all active crawl jobs for the authenticated team. Use when you need to see which crawl operations are currently running. | | `FIRECRAWL_CRAWL_PARAMS_PREVIEW` | Preview crawl parameters | Preview crawl parameters before starting a crawl by generating optimal configuration from natural language instructions. Use this tool to understand what crawl settings will be applied based on your requirements before executing a full crawl operation. The endpoint intelligently interprets natural language prompts to configure crawl parameters like include/exclude paths, depth limits, and domain scope. | | `FIRECRAWL_CRAWL_V2` | Start a web crawl (v2) [NEW] | [NEW v2 API] Initiates a Firecrawl v2 web crawl with enhanced features over v1: natural language prompts for automatic crawler configuration, crawlEntireDomain for sibling/parent page discovery, better depth control with maxDiscoveryDepth, subdomain support, and full webhook configuration. Polls until crawl is complete. | | `FIRECRAWL_CREDIT_USAGE_GET` | Get team credit usage | Tool to get current team credit usage information. Use when you need to check remaining credits or billing period details. | | `FIRECRAWL_CREDIT_USAGE_GET_HISTORICAL` | Get historical team credit usage | Tool to retrieve historical team credit usage on a monthly basis. Use when you need to analyze credit consumption patterns over time, optionally segmented by API key. | | `FIRECRAWL_EXTRACT` | Extract structured data | Extracts structured data from web pages by initiating an extraction job and polling for completion; requires a natural language `prompt` or a JSON `schema` (one must be provided). | | `FIRECRAWL_EXTRACT_GET` | Get extract job status | Tool to retrieve the status and results of a previously submitted extract job. Use when you need to check the progress or get the final results of an extraction operation. | | `FIRECRAWL_GET_AGENT_STATUS` | Get agent job status | Tool to get the status and results of an agent job. Use when you need to check if an agent job has completed and retrieve the collected data. Agent jobs autonomously search, navigate, and extract data from the web. | | `FIRECRAWL_GET_DEEP_RESEARCH_STATUS` | Get deep research status | Retrieves the status and results of a deep research job by its ID. Use when you need to check the progress or retrieve the final analysis of a deep research operation. | | `FIRECRAWL_GET_THE_STATUS_OF_A_CRAWL_JOB` | Get the status of a crawl job | Retrieves the current status, progress, and details of a web crawl job, using the job ID obtained when the crawl was initiated. | | `FIRECRAWL_LLMS_TXT_GENERATE` | Generate LLMs.txt for a website | Initiates an async job to generate an LLMs.txt file for a website, converting web content into LLM-friendly format. Returns a job ID to check status and retrieve results. Use when you need to create a standardized, machine-readable representation of website content for language models. | | `FIRECRAWL_LLMS_TXT_GET` | Get LLMs.txt generation job status | Tool to get the status and results of an LLMs.txt generation job. Use when you need to check if a job has completed and retrieve the generated content. | | `FIRECRAWL_MAP_MULTIPLE_URLS_BASED_ON_OPTIONS` | Map multiple URLs | Maps a website by discovering URLs from a starting base URL, with options to customize the crawl via search query, subdomain inclusion, sitemap handling, and result limits; search effectiveness is site-dependent. | | `FIRECRAWL_QUEUE_GET` | Get team queue status | Tool to retrieve metrics about the team's scrape queue. Use when you need to check queue status, job counts, or concurrency limits. | | `FIRECRAWL_SCRAPE` | Scrape URL | Scrapes a publicly accessible URL, optionally performing pre-scrape browser actions or extracting structured JSON using an LLM, to retrieve content in specified formats. | | `FIRECRAWL_SEARCH` | Search | Performs a web search for a query, scrapes content from the top search results using Firecrawl, and returns details in specified formats. | | `FIRECRAWL_START_AGENT` | Start an agent job | Tool to start an agent job for agentic web extraction with multi-page navigation and interaction capabilities. Use when you need to autonomously gather data from the web with complex navigation requirements. The agent can search, navigate, and extract information across multiple pages based on your natural language prompt. | | `FIRECRAWL_TOKEN_USAGE_GET` | Get team token usage | Tool to retrieve the current team's token usage and balance information for Firecrawl's Extract feature. Use when you need to check remaining token credits, plan allocation, or billing period details. | | `FIRECRAWL_TOKEN_USAGE_GET_HISTORICAL` | Get historical team token usage | Tool to retrieve historical team token usage on a monthly basis. Use when you need to analyze token consumption patterns over time, optionally segmented by API key. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Firecrawl MCP server is an implementation of the Model Context Protocol that connects your AI agent to Firecrawl. It provides structured and secure access so your agent can perform Firecrawl operations on your behalf through a secure, permission-based interface. 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: - Composio API Key and Claude/Anthropic API Key - Primary know-how of Claude Agents SDK - A Firecrawl account - Some knowledge of Python ### 1. Getting API Keys for Claude/Anthropic and Composio Claude/Anthropic API Key - Go to the [Anthropic Console](https://console.anthropic.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models. - Keep the API key safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install dependencies No description provided. ```python pip install composio-anthropic claude-agent-sdk python-dotenv ``` ```typescript npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's happening: - COMPOSIO_API_KEY authenticates with Composio - USER_ID identifies the user for session management - ANTHROPIC_API_KEY authenticates with Anthropic/Claude ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here ANTHROPIC_API_KEY=your_anthropic_api_key_here ``` ### 4. Import dependencies No description provided. ```python import asyncio from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions import os from composio import Composio from dotenv import load_dotenv load_dotenv() ``` ```typescript import 'dotenv/config'; import readline from 'node:readline'; import { Composio } from '@composio/core'; import { query, type Options } from "@anthropic-ai/claude-agent-sdk"; dotenv.config(); ``` ### 5. Create a Composio instance and Tool Router session No description provided. ```python async def chat_with_remote_mcp(): api_key = os.getenv("COMPOSIO_API_KEY") if not api_key: raise RuntimeError("COMPOSIO_API_KEY is not set") composio = Composio(api_key=api_key) # Create Tool Router session for Firecrawl mcp_server = composio.create( user_id=os.getenv("USER_ID"), toolkits=["firecrawl"] ) url = mcp_server.mcp.url if not url: raise ValueError("Session URL not found") ``` ```typescript async function chat() { 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 composio = new Composio({ apiKey: COMPOSIO_API_KEY }); // Create Tool Router session for Firecrawl const session = await composio.create(USER_ID, { toolkits: ['firecrawl'], }); const mcpUrl = session?.mcp.url; ``` ### 6. Configure Claude Agent with MCP No description provided. ```python # Configure remote MCP server for Claude options = ClaudeAgentOptions( permission_mode="bypassPermissions", mcp_servers={ "composio": { "type": "http", "url": url, "headers": { "x-api-key": os.getenv("COMPOSIO_API_KEY") } } }, system_prompt="You are a helpful assistant with access to Firecrawl tools via Composio.", max_turns=10 ) ``` ```typescript const options: Options = { permissionMode: 'bypassPermissions', mcpServers: { composio: { type: 'http', url: mcpUrl, headers: { 'x-api-key': COMPOSIO_API_KEY } } }, systemPrompt: 'You are a helpful assistant with access to Firecrawl tools via Composio.', maxTurns: 10, }; ``` ### 7. Create client and start chat loop No description provided. ```python # Create client with context manager async with ClaudeSDKClient(options=options) as client: print("\nChat started. Type 'exit' or 'quit' to end.\n") # Main chat loop while True: user_input = input("You: ").strip() if user_input.lower() in {"exit", "quit"}: print("Goodbye!") break # Send query await client.query(user_input) # Receive and print response print("Claude: ", end="", flush=True) async for message in client.receive_response(): if hasattr(message, "content"): for block in message.content: if hasattr(block, "text"): print(block.text, end="", flush=True) print() ``` ```typescript const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: 'You: ' }); console.log('\nChat started. Type "exit" to quit.\n'); let isProcessing = false; async function ask(prompt: string) { isProcessing = true; rl.pause(); process.stdout.write('Claude is thinking...'); const stream = query({ prompt, options }); let firstChunk = true; for await (const msg of stream) { const content = (msg as any).message?.content || (msg as any).content; if (Array.isArray(content)) { for (const block of content) { if (block.type === 'text' && block.text) { if (firstChunk) { process.stdout.write('\r\x1b[K'); process.stdout.write('Claude: '); firstChunk = false; } process.stdout.write(block.text); } } } } process.stdout.write('\n\n'); isProcessing = false; rl.resume(); rl.prompt(); } rl.on('line', async (line) => { if (isProcessing) return; const input = line.trim(); if (input === 'exit') { rl.close(); process.exit(0); } if (input) await ask(input); else rl.prompt(); }); await ask('What can you help me with?'); } ``` ### 8. Run the application No description provided. ```python if __name__ == "__main__": asyncio.run(chat_with_remote_mcp()) ``` ```typescript try { await chat(); } catch (error) { console.error(error); process.exit(1); } ``` ## Complete Code ```python import asyncio from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions import os from composio import Composio from dotenv import load_dotenv load_dotenv() async def chat_with_remote_mcp(): api_key = os.getenv("COMPOSIO_API_KEY") if not api_key: raise RuntimeError("COMPOSIO_API_KEY is not set") composio = Composio(api_key=api_key) # Create Tool Router session for Firecrawl mcp_server = composio.create( user_id=os.getenv("USER_ID"), toolkits=["firecrawl"] ) url = mcp_server.mcp.url if not url: raise ValueError("Session URL not found") # Configure remote MCP server for Claude options = ClaudeAgentOptions( permission_mode="bypassPermissions", mcp_servers={ "composio": { "type": "http", "url": url, "headers": { "x-api-key": os.getenv("COMPOSIO_API_KEY") } } }, system_prompt="You are a helpful assistant with access to Firecrawl tools via Composio.", max_turns=10 ) # Create client with context manager async with ClaudeSDKClient(options=options) as client: print("\nChat started. Type 'exit' or 'quit' to end.\n") # Main chat loop while True: user_input = input("You: ").strip() if user_input.lower() in {"exit", "quit"}: print("Goodbye!") break # Send query await client.query(user_input) # Receive and print response print("Claude: ", end="", flush=True) async for message in client.receive_response(): if hasattr(message, "content"): for block in message.content: if hasattr(block, "text"): print(block.text, end="", flush=True) print() if __name__ == "__main__": asyncio.run(chat_with_remote_mcp()) ``` ```typescript import 'dotenv/config'; import readline from 'node:readline'; import { Composio } from '@composio/core'; import { query, type Options } from "@anthropic-ai/claude-agent-sdk"; async function chat() { 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 composio = new Composio({ apiKey: COMPOSIO_API_KEY }); const session = await composio.create(USER_ID, { toolkits: ['firecrawl'] }); const mcp_url = session?.mcp.url; const options: Options = { permissionMode: 'bypassPermissions', mcpServers: { composio: { type: 'http', url: mcp_url, headers: { 'x-api-key': COMPOSIO_API_KEY } } }, systemPrompt: 'You are a helpful assistant with access to Firecrawl tools via Composio.', maxTurns: 10, }; const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: 'You: ' }); console.log('\nChat started. Type "exit" to quit.\n'); let isProcessing = false; async function ask(prompt: string) { isProcessing = true; rl.pause(); process.stdout.write('Claude is thinking...'); const stream = query({ prompt, options }); let firstChunk = true; for await (const msg of stream) { const content = (msg as any).message?.content || (msg as any).content; if (Array.isArray(content)) { for (const block of content) { if (block.type === 'text' && block.text) { if (firstChunk) { process.stdout.write('\r\x1b[K'); process.stdout.write('Claude: '); firstChunk = false; } process.stdout.write(block.text); } } } } process.stdout.write('\n\n'); isProcessing = false; rl.resume(); rl.prompt(); } rl.on('line', async (line) => { if (isProcessing) return; const input = line.trim(); if (input === 'exit') { rl.close(); process.exit(0); } if (input) await ask(input); else rl.prompt(); }); await ask('What can you help me with?'); } try { await chat(); } catch (error) { console.error(error); process.exit(1); } ``` ## Conclusion You've successfully built a Claude Agent SDK agent that can interact with Firecrawl through Composio's Tool Router. Key features: - Native MCP support through Claude's agent framework - Streaming responses for real-time interaction - Permission bypass for smooth automated workflows You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent. ## How to build Firecrawl MCP Agent with another framework - [Claude Code](https://composio.dev/toolkits/firecrawl/framework/claude-code) - [Cursor](https://composio.dev/toolkits/firecrawl/framework/cursor) - [ChatGPT](https://composio.dev/toolkits/firecrawl/framework/chatgpt) - [Claude Cowork](https://composio.dev/toolkits/firecrawl/framework/claude-cowork) - [Antigravity](https://composio.dev/toolkits/firecrawl/framework/antigravity) - [OpenAI Agents SDK](https://composio.dev/toolkits/firecrawl/framework/open-ai-agents-sdk) - [Grok Bot](https://composio.dev/toolkits/firecrawl/framework/grok-bot) - [Muse](https://composio.dev/toolkits/firecrawl/framework/muse) - [Codex](https://composio.dev/toolkits/firecrawl/framework/codex) - [Grok Build](https://composio.dev/toolkits/firecrawl/framework/grok-build) - [VS Code](https://composio.dev/toolkits/firecrawl/framework/vscode) - [OpenCode](https://composio.dev/toolkits/firecrawl/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/firecrawl/framework/openclaw) - [Hermes](https://composio.dev/toolkits/firecrawl/framework/hermes-agent) - [Atomic Agent](https://composio.dev/toolkits/firecrawl/framework/atomic-agent) - [Pi](https://composio.dev/toolkits/firecrawl/framework/pi-agent) - [DeepSeek Harness](https://composio.dev/toolkits/firecrawl/framework/deepseek) - [Google ADK](https://composio.dev/toolkits/firecrawl/framework/google-adk) - [LangChain](https://composio.dev/toolkits/firecrawl/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/firecrawl/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/firecrawl/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/firecrawl/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/firecrawl/framework/crew-ai) - [Pydantic AI](https://composio.dev/toolkits/firecrawl/framework/pydantic-ai) - [AutoGen](https://composio.dev/toolkits/firecrawl/framework/autogen) ## Related Toolkits - [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. - [Ahrefs MCP](https://composio.dev/toolkits/ahrefs_mcp) - Ahrefs MCP is Ahrefs' hosted MCP server for SEO data and insights. Use it to access backlinks, organic metrics, keyword research, and competitor analysis. - [Akta](https://composio.dev/toolkits/akta) - Akta is a company intelligence platform providing enrichment, news, and alternative business signals. It helps teams build targeted company lists and enrich data-driven workflows. - [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. - [Amplitude MCP](https://composio.dev/toolkits/amplitude_mcp) - Amplitude MCP is Amplitude's product analytics service for tracking user behavior and product metrics. Use it to centralize product data and manage charts, dashboards, cohorts, experiments, and taxonomy. - [Audioscrape MCP](https://composio.dev/toolkits/audioscrape_mcp) - Audioscrape MCP lets agents search and retrieve speaker-attributed audio, transcripts, entities, and citations from public and workspace content. Use it to surface searchable, speaker-labeled audio and rich metadata for research, meetings, and content discovery. - [Baremetrics](https://composio.dev/toolkits/baremetrics) - Baremetrics is a subscription analytics platform for recurring-revenue businesses. It helps teams track MRR, churn, customers, and revenue trends in one place. - [Bing Webmaster Tools](https://composio.dev/toolkits/bing_webmaster_tools) - Bing Webmaster Tools is Microsoft's search console for site performance, crawling, indexing, URL submission, and verified site management. It helps site owners understand Bing Search visibility and fix issues that affect organic traffic. - [Bread & Butter](https://composio.dev/toolkits/bread_butter) - Bread & Butter is a lead-intelligence and identity platform for website visitor tracking, user profiles, attribution, authentication, and conversion workflows. It helps teams understand who is visiting, where leads come from, and how users convert. - [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. - [BSC Designer](https://composio.dev/toolkits/bsc_designer) - BSC Designer is a strategy execution platform for balanced scorecards, KPIs, dashboards, and strategy maps. It helps teams turn goals into measurable performance plans they can track over time. - [Chameleon](https://composio.dev/toolkits/chameleon) - Chameleon is a product adoption platform for building in-app experiences, managing customer data, and analyzing user engagement. It helps teams improve onboarding, feature discovery, and product adoption with targeted user experiences. - [Chartly](https://composio.dev/toolkits/chartly) - Chartly renders Chart.js configurations as PNG or SVG images and creates permanent chart URLs for sharing and embedding. Share and embed charts easily with stable image URLs and downloadable vector graphics. - [ChartMogul](https://composio.dev/toolkits/chartmogul) - ChartMogul is a subscription analytics and revenue data platform. It helps teams monitor MRR, churn, customer segments, and billing metrics. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Firecrawl MCP? With a standalone Firecrawl MCP server, the agents and LLMs can only access a fixed set of Firecrawl tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Firecrawl and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Claude Agent SDK? Yes, you can. Claude Agent SDK 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 Firecrawl tools. ### Can I manage the permissions and scopes for Firecrawl while using Tool Router? Yes, absolutely. You can configure which Firecrawl 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 Firecrawl data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)