SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to connect Browser Use to Claude

Connect Claude Web, Desktop and Cowork to Browser Use MCP. Capture screenshots of checkout pages hourly, fill and submit job application forms, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Browser Use logoBrowser Use
Api Key

Browser Use Cloud provides hosted browser agents, managed browser sessions, workspaces, profiles, and integrations. Use it to run browser-based automations at scale with managed sessions and profiles.

39 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Browser Use account to Claude via Composio Connect, enabling it to capture screenshots of checkout pages hourly, fill and submit job application forms, scrape product prices across competitor sites, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Browser Use with

ChatGPTHermesAtomic Agent

Connecting Browser Use to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Browser Use account

Back in Claude, ask it to connect to Browser Use or give it any Browser Use-related task.

For example, ask Claude to:

  • "Capture screenshots of checkout pages hourly"
  • "Fill and submit job application forms"
  • "Scrape product prices across competitor sites"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Browser Use account is ready to use.

What is the Browser Use Claude Connector, and what's possible with it?

The Browser Use MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Browser Use account. It provides structured and secure access so your agent can perform Browser Use operations on your behalf.

Troubleshooting

1. Why does Claude not use the Composio connector for Browser Use?

The connector can show as connected, but Claude must use it in each Browser Use conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Browser Use again.

2. Why does Claude show an MCP server error before Browser Use connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Browser Use.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Browser Use.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Browser Use authorization link not work?

The Composio connector is one server. Your Browser Use account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Browser Use connection.
  • Composio creates a fresh Browser Use authorization link.
  • Open that link in your browser and finish the Browser Use sign-in.

4. Why do Browser Use actions fail after they worked before?

The Browser Use connection can expire or lose permission.

  • Ask Claude to inspect the Browser Use connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Browser Use account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Browser Use.
  • If the action still fails with a permission error, check that the connected account has that permission in Browser Use itself.

5. How do I switch to a different Browser Use account?

Claude can manage the Browser Use connection for you.

  • Ask Claude to disconnect or delete the current Browser Use account.
  • Ask Claude to connect Browser Use again.
  • Open the new Composio authorization link for Browser Use.
  • Sign in with the other Browser Use account in the browser.
  • After the account connects, ask Claude to retry the Browser Use task.

6. Why is my Browser Use connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Browser Use connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Browser Use tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Browser Use.
TOOLS

Supported Tools

Every Browser Use action and event your agent gets out of the box.

Archive Workspace

Archive a workspace so it is no longer readable through the workspace API.

Cancel Queued Message

Cancel a queued session message while it is still pending.

Cancel Run

Idempotently cancel an in-flight browser-agent run; completed work cannot be resumed by this call.

Create Browser Session

Launch a paid managed browser for direct CDP control; time is prepaid and unused time is refunded when the browser is stopped.

Create Browser Profile

Create a persistent browser profile for reusable cookies and browser state.

Create Workspace

Create an empty workspace for browser-run input files and outputs.

Delete Browser Profile

Permanently delete a persistent browser profile and its configuration.

Delete Session

Soft-delete a conversation session and cancel its active run and pending messages.

Delete Workspace File

Permanently delete one exact relative file path from a workspace.

Disconnect Integration

Disconnect a downstream provider from the Browser Use project, revoking its availability to future runs.

Get Browser Session

Get a managed browser's status, control URLs, costs, metadata, and recording state.

Get Integration Status

Check whether one downstream integration provider is connected to the Browser Use project.

Get Browser Profile

Get one persistent browser profile's metadata and observed cookie domains.

Get Queued Message

Get one queued session message, including its terminal handoff state.

Get Run

Get a run's full result, usage, and optionally its ordered input-file attachments.

Get Run Status

Read a run's lightweight indexed status for caller-controlled polling.

Get Session

Get one conversation session's latest-run summary and busy or idle status.

Get Session Feedback

Get all feedback votes recorded for a conversation session.

Get Session Share

Get a session's current or inactive public share-link state without changing its exposure.

Get Workspace

Get workspace metadata and optionally its current storage use and plan quota.

List Browser Downloads

List one page of files downloaded by a managed browser, optionally including presigned URLs that expire after 15 minutes.

List Browser Sessions

List managed browser sessions with status, metadata, and agent-session filters, one page at a time.

List Integration Categories

List the category names used to organize Browser Use integration providers.

List Integrations

Search Browser Use integration providers and filter by popularity or project connection status, one page at a time.

List Run Payment Methods

Return AgentCard wallets and the project's active Stripe Link connection that browser runs can use for payments.

List Browser Profiles

List or search persistent browser profiles one page at a time.

List Run Events

Read one page of a run's execution events incrementally, with optional event output payloads.

List Runs

List browser-agent runs, optionally restricted to one conversation session, one page at a time.

List Session Queue

List pending and recently delivered messages for a conversation session, including transcript cutoffs created by steering interrupts.

List Sessions

List conversation sessions with each session's latest run and busy or idle status, one page at a time.

List Workspace Files

List one page of files in a workspace by path prefix, optionally including temporary download URLs.

Queue Session Message

Queue a follow-up for a conversation session, optionally interrupting its active run; dispatch may consume credits and trigger external browser work.

Set Session Feedback

Set, replace, or clear feedback for one session chat item.

Set Session Sharing

Enable or disable a session's stable public share link, creating or reactivating it when enabled.

Start Browser Run

Start an asynchronous hosted browser-agent task that may make irreversible changes on external sites and consume project credits.

Stop Browser Session

Stop a managed browser session and refund unused prepaid time subject to the one-minute minimum charge.

Update Browser Profile

Update a persistent browser profile's name, user identifier, or both.

Update Session

Rename a conversation session or explicitly clear its title.

Update Workspace

Rename a workspace or explicitly clear its name.

FRAMEWORKS

How to build Browser Use MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Browser Use MCP with ChatGPT

Hermes logo

Hermes

Use Browser Use MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Browser Use MCP with Atomic Agent

FAQ

Frequently asked questions

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

Yes, you can. Claude Cowork 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 Browser Use tools.

Yes, absolutely. You can configure which Browser Use 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.

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 Browser Use data and credentials are handled as safely as possible.

Start with Browser Use.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Browser Use tool your agent needs.Free to start.

Start building