How to integrate Browser Use MCP with Atomic Agent

Connect Atomic Agent 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.

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

Atomic Agent is an open-source AI agent that runs on your machine and supports local models through llama.cpp. Connect it to 1,500+ apps through Composio, including Browser Use.

This guide uses Atomic Agent's built-in Composio integration. You need Atomic Agent v0.5.6 or later, your own Composio API key, and a Browser Use account. See the Atomic Agent documentation for installation instructions.

Also integrate Browser Use with

How Atomic Agent connects to Browser Use

Atomic Agent connects to Composio's Tool Router over Streamable HTTP MCP. It discovers the tools needed for your request, and Composio handles account authentication.

Execution and account-connection tools follow Atomic Agent's configured approval policy. Review any approval prompt before allowing an action on your connected account.

Connect Browser Use to Atomic Agent

  1. Sign up or sign in to the Composio dashboard. Copy your API key.
  2. In Atomic Agent, open the Integrations tab and select Composio. Select API key, press e, paste the key, and press Enter. The tools become available immediately, without a restart.
  3. Ask Atomic Agent to do something in Browser Use. It searches Composio for the right tool.
  4. On first use, open the sign-in link returned in the chat. Connect your Browser Use account, then return to Atomic Agent to continue.

Headless setup

Add the following line to ~/.atomic-agent/.env, replacing YOUR_COMPOSIO_API_KEY with your key. Start Atomic Agent after saving the file.

bash
COMPOSIO_API_KEY=YOUR_COMPOSIO_API_KEY

What is the Browser Use MCP server, 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.

Use Browser Use from Atomic Agent

With your account connected, ask Atomic Agent to work with Browser Use in natural language. You can connect more apps through the same Composio integration as you need them.

Visit the Atomic Agent website or inspect the Atomic Agent source code.

Troubleshooting

Why is my API key rejected?

Copy the key directly from the Composio dashboard. Atomic Agent requires ASCII characters because it sends the key in an HTTP header. Remove any extra characters introduced when copying.

Why are Composio tools unavailable after saving a key?

Check that you use Atomic Agent v0.5.6 or later and that Composio is enabled in your configuration. A "composio": { "enabled": false } setting disables the integration while keeping the saved key on disk.

Does Composio have a free plan?

The Hobby plan includes 100,000 tool calls per month. Composio-managed OAuth apps have a lower included allowance. See Composio pricing for the current limits that apply to your connection.

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.

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. Atomic Agent 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