# How to integrate Browserbase tool MCP with Claude Code ```json { "title": "How to integrate Browserbase tool MCP with Claude Code", "toolkit": "Browserbase tool", "toolkit_slug": "browserbase_tool", "framework": "Claude Code", "framework_slug": "claude-code", "url": "https://composio.dev/toolkits/browserbase_tool/framework/claude-code", "markdown_url": "https://composio.dev/toolkits/browserbase_tool/framework/claude-code.md", "updated_at": "2026-05-12T10:04:17.094Z" } ``` ## Introduction Manage your Browserbase tool 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 Browserbase tool with - [OpenAI Agents SDK](https://composio.dev/toolkits/browserbase_tool/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/browserbase_tool/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/browserbase_tool/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/browserbase_tool/framework/codex) - [OpenClaw](https://composio.dev/toolkits/browserbase_tool/framework/openclaw) - [Hermes](https://composio.dev/toolkits/browserbase_tool/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/browserbase_tool/framework/cli) - [Google ADK](https://composio.dev/toolkits/browserbase_tool/framework/google-adk) - [LangChain](https://composio.dev/toolkits/browserbase_tool/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/browserbase_tool/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/browserbase_tool/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/browserbase_tool/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/browserbase_tool/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 Browserbase tool to Claude Code ### Connecting Browserbase tool 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 Browserbase tool MCP server, and what's possible with it? The Browserbase tool MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Browserbase account. It provides structured and secure access to your headless browser environments, so your agent can launch browser sessions, capture artifacts, retrieve debug info, and manage session contexts—all at scale and with zero manual setup. - Automated browser session management: Instantly create, retrieve, and update browser sessions to run automated browsing tasks in isolated environments. - Headless testing and monitoring: Let your agent spin up new browser contexts for advanced testing, monitoring, or web scraping workflows—no local infrastructure needed. - Artifact and log retrieval: Automatically collect session artifacts (like screenshots, HAR files, or logs) after browser tasks complete for audit, debugging, or analytics purposes. - Real-time session debugging: Fetch live debug URLs so your agent (or you!) can connect and troubleshoot active sessions on demand. - Comprehensive session tracking: List, filter, and inspect all your browser sessions, including metadata, statuses, and historical activity, to stay on top of your automation fleet. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `BROWSERBASE_TOOL_CONTEXTS_CREATE` | Create a new browser context | Tool to create a new browser context. Use when you need to obtain upload credentials for a custom user-data-directory in a project. | | `BROWSERBASE_TOOL_CONTEXTS_GET` | Retrieve a browser context | Tool to retrieve details of a specific browser context. Use when you have a context ID and need its metadata. | | `BROWSERBASE_TOOL_CONTEXTS_UPDATE` | Update Browser Context | Tool to update a specific browser context. Use when you need fresh upload URL and encryption details for an existing context, after obtaining a valid context ID. | | `BROWSERBASE_TOOL_CREATE_BROWSER_SESSION` | Create Browser Session | Tool to create a new browser session. Use when you need an isolated browser context before performing any page interactions. | | `BROWSERBASE_TOOL_DELETE_CONTEXT` | Delete a browser context | Tool to delete a browser context and all its stored data (cookies, localStorage, etc.). Use when you need to permanently remove a context. | | `BROWSERBASE_TOOL_DELETE_EXTENSION` | Delete a browser extension | Tool to delete an uploaded browser extension by its ID. Use when you need to remove an extension from Browserbase. | | `BROWSERBASE_TOOL_DELETE_SESSION_DOWNLOADS` | Delete Session Downloads | Tool to delete all file downloads from a specific browser session. Use when you need to clean up session artifacts or free storage space. | | `BROWSERBASE_TOOL_GET_EXTENSION` | Retrieve a browser extension | Tool to retrieve details of a specific browser extension. Use when you have an extension ID and need its metadata (file name, timestamps, project ID). | | `BROWSERBASE_TOOL_GET_PROJECT` | Retrieve a project | Tool to retrieve details of a specific project including settings and configuration. Use when you have a project ID and need its metadata. | | `BROWSERBASE_TOOL_GET_PROJECT_USAGE` | Get project usage statistics | Tool to retrieve usage statistics for a project including browser minutes and proxy bytes consumed. Use when you need to monitor or track resource usage for a specific project. | | `BROWSERBASE_TOOL_LIST_PROJECTS` | List Projects | Tool to list all projects for the authenticated account. Use when you need to retrieve all projects associated with the current API key. | | `BROWSERBASE_TOOL_SESSIONS_GET` | Retrieve a browser session | Tool to retrieve details of a specific browser session. Use when you have a session ID and need its metadata (status, URLs, timestamps). | | `BROWSERBASE_TOOL_SESSIONS_GET_DEBUG` | Retrieve Session Debug URLs | Tool to retrieve live debug URLs for a specific session. Use when you need to connect to a running session for debugging. | | `BROWSERBASE_TOOL_SESSIONS_GET_DOWNLOADS` | Download Session Artifacts | Tool to download files from a specific session. Use after session completion to retrieve all generated artifacts in a ZIP archive. | | `BROWSERBASE_TOOL_SESSIONS_GET_LOGS` | Retrieve Session Logs | Tool to retrieve logs of a specific session. Use after actions in a session to inspect network events and data exchange. | | `BROWSERBASE_TOOL_SESSIONS_LIST` | List Browser Sessions | Tool to list all browser sessions. Use when you need to retrieve sessions with optional filtering by status or metadata query. | | `BROWSERBASE_TOOL_SESSIONS_UPDATE` | Update Browser Session | Tool to update the status of a specific browser session. Use when you need to request session completion before timeout to avoid additional charges. | | `BROWSERBASE_TOOL_UPLOAD_EXTENSION` | Upload Browser Extension | Tool to upload a browser extension for use in sessions. Supports Chrome extension format (ZIP). Use when you need to add custom browser extensions to your Browserbase project. | | `BROWSERBASE_TOOL_UPLOAD_SESSION_FILE` | Upload File to Session | Tool to upload files to a browser session for file input operations. Use when you need to make files available for file input fields or downloads within a browser automation session. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Browserbase tool 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 Browserbase tool account. It provides structured and secure access so Claude can perform Browserbase tool 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 Browserbase tool 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=["browserbase_tool"], ) 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 browserbase_tool-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: ['browserbase_tool'], }); 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 browserbase_tool-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 Browserbase tool 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 (browserbase_tool-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 browserbase_tool-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 Browserbase tool MCP server is properly configured. - This command lists all MCP servers registered with Claude Code - You should see your browserbase_tool-composio entry in the list - This confirms that Claude Code can now access Browserbase tool tools If everything is wired up, you should see your browserbase_tool-composio entry listed: ```bash claude mcp list ``` ### 9. Authenticate Browserbase tool The first time you try to use Browserbase tool tools, you'll be prompted to authenticate. - Claude Code will detect that you need to authenticate with Browserbase tool - It will show you an authentication link - Open the link in your browser (or copy/paste it) - Complete the Browserbase tool authorization flow - Return to the terminal and start using Browserbase tool through Claude Code Once authenticated, you can ask Claude Code to perform Browserbase tool operations in natural language. For example: - "Start a new headless browser session now" - "Download all artifacts from last session" - "Retrieve debug URLs for active sessions" ## 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=["browserbase_tool"], ) 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 browserbase_tool-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: ['browserbase_tool'], }); 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 browserbase_tool-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ## Conclusion You've successfully integrated Browserbase tool with Claude Code using Composio's MCP server. Now you can interact with Browserbase tool directly from your terminal using natural language commands. Key features of this setup: - Terminal-native experience without switching contexts - Natural language commands for Browserbase tool 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 Browserbase tool 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 Browserbase tool MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/browserbase_tool/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/browserbase_tool/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/browserbase_tool/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/browserbase_tool/framework/codex) - [OpenClaw](https://composio.dev/toolkits/browserbase_tool/framework/openclaw) - [Hermes](https://composio.dev/toolkits/browserbase_tool/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/browserbase_tool/framework/cli) - [Google ADK](https://composio.dev/toolkits/browserbase_tool/framework/google-adk) - [LangChain](https://composio.dev/toolkits/browserbase_tool/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/browserbase_tool/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/browserbase_tool/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/browserbase_tool/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/browserbase_tool/framework/crew-ai) ## Related Toolkits - [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure. - [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms. - [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place. - [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences. - [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses. - [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure. - [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure. - [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction. - [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting. - [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache. - [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence. - [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place. - [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines. - [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure. - [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code. - [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows. - [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights. - [Bitbucket](https://composio.dev/toolkits/bitbucket) - Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews. - [Blazemeter](https://composio.dev/toolkits/blazemeter) - Blazemeter is a continuous testing platform for web and mobile app performance. It empowers teams to automate and analyze large-scale tests with ease. - [Blocknative](https://composio.dev/toolkits/blocknative) - Blocknative delivers real-time mempool monitoring and transaction management for public blockchains. Instantly track pending transactions and optimize blockchain interactions with live data. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Browserbase tool MCP? With a standalone Browserbase tool MCP server, the agents and LLMs can only access a fixed set of Browserbase tool tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Browserbase tool 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 Browserbase tool tools. ### Can I manage the permissions and scopes for Browserbase tool while using Tool Router? Yes, absolutely. You can configure which Browserbase tool 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 Browserbase tool data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)