How to connect Browserbase tool to Muse

Connect Muse to Browserbase tool MCP. Start a new headless browser session now, download all artifacts from last session, and more using natural language, with authentication handled for you.

Browserbase tool logoBrowserbase tool
Api Key

Browserbase is a serverless platform for running and managing headless browsers at scale. It lets you automate and monitor browser tasks with Playwright, Puppeteer, and Selenium—no infrastructure headaches.

19 Tools

Introduction

Muse is Meta's AI assistant. It can connect to outside tools through custom connectors, which use the Model Context Protocol (MCP).

This guide explains how to connect Browserbase tool to Muse using Composio Connect, which handles OAuth, token refresh, and reliability so you do not have to. You add Composio as a custom connector once, then ask Muse to work with Browserbase tool in plain language.

Also integrate Browserbase tool with

Why use Composio?

  • Cross-app workflows across 1,500+ apps from a single plugin layer.
  • On-demand tool loading so Muse only loads the tools needed for the current task.
  • Programmatic tool calling through a remote workbench for complex, multi-step workflows.
  • Multi-account support so users can connect and switch between multiple accounts for the same app.
  • Shared account access so teams or agents can work through common business accounts and service connections.
  • Managed authentication with OAuth handling, credential storage, and token refresh managed by Composio.
  • Safer credential handling so app credentials stay outside the model context and tool responses.
  • User-level account isolation so actions run against the correct connected account instead of mixing user access.

Connecting Browserbase tool to Muse

You add Composio to Muse once as a custom connector, then connect Browserbase tool from the chat.

1. Ask Muse to connect to Composio

Start a new Muse chat and send this message. Muse builds the connector and shows a button to add your API key.

bash
Create a Custom Connector for the Composio remote MCP server and connect to it:
- Name: Composio
- Transport: remote streamable HTTP
- URL: https://connect.composio.dev/mcp
- Auth: API key sent in the x-consumer-api-key header
Open the secure credentials store so I can enter the API key there, not in this chat. Then list its tools to confirm the connection works.

2. Copy your API key

Open the Muse page in your Composio dashboard and copy your API key. It starts with ck_.

Don't paste it into the chat. It goes in Muse's secure credentials store in the next step.

3. Add your API key in the secure credentials store

Tap the button Muse shows to open Add custom connector, paste your API key, then tap Add. Muse lists the Composio tools once it connects.

Muse secure credentials store with the connect.composio.dev URL, an API Key field, and the Add button

4. Connect your Browserbase tool account

Back in the chat, ask Muse to connect to Browserbase tool or give it any Browserbase tool task.

For example, ask it to:

  • "Start a new headless browser session now"
  • "Download all artifacts from last session"
  • "Retrieve debug URLs for active sessions"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Muse, and your Browserbase tool account is ready to use.

What is the Browserbase tool MCP server, and what's possible with it?

The Browserbase 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 browser sessions, contexts, projects, recordings, logs, files, and extensions, so your agent can create sessions, manage reusable contexts, inspect browser activity, retrieve recordings, and monitor project usage on your behalf.

  • Browser session management: Have your agent create isolated browser sessions, check their status, list recent sessions, and release running sessions when work is complete.
  • Reusable browser contexts: Let the agent create, inspect, and update browser contexts that preserve settings across multiple sessions.
  • Session monitoring and debugging: Direct your agent to retrieve live debugging access, review captured network activity, and inspect session logs.
  • Recordings and session artifacts: Instruct your agent to retrieve session replays, request downloadable recordings, and download generated session files.
  • Projects, files, and extensions: Have your agent review projects and usage, upload files for browser forms, and upload or inspect browser extensions.

Way Forward

Now that Browserbase tool is connected, extend your setup by connecting the other apps you already use every day, so Muse can run true cross-app workflows end to end.

  • Connect Calendar to turn threads into scheduled meetings automatically.
  • Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
  • Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
  • Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.

Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single connection, Muse can coordinate multiple tools safely and reliably in one conversation.

Troubleshooting

1. Why doesn't Muse show a button to add my API key?

Muse shows the button only when you ask it to open the secure credentials store.

  • Start a new chat.
  • Send the message from step 1 exactly as written.
  • If Muse asks for the key in the chat, do not paste it. Ask Muse to open the secure credentials store.

2. Why does the Composio connection fail after I add my API key?

The key or the connector settings are not correct.

  • Copy the full key from the Composio dashboard. It starts with ck_.
  • Make sure the URL is https://connect.composio.dev/mcp and the header is x-consumer-api-key.
  • Remove the Composio connector in Muse settings, then do steps 1 to 3 again.

3. Why doesn't Muse use the Composio tools for Browserbase tool?

Muse may not pick the Composio connector for the request.

  • Ask Muse to list its Composio tools.
  • Name Composio and Browserbase tool in your request, for example: Use Composio to connect to Browserbase tool.
  • If it still does not work, start a new chat and try again.

4. Why does Muse ask me to connect Browserbase tool again?

Your Browserbase tool connection expired or was removed.

  • Open the link Muse gives you and sign in to Browserbase tool again.
  • Check that the Browserbase tool connection shows as ACTIVE in the Composio dashboard.

5. What do I do if I pasted my API key into the chat?

Treat the key as exposed.

  • Create a new API key in the Composio dashboard and delete the old one.
  • Add the new key in Muse's secure credentials store, not in the chat.
TOOLS

Supported Tools

Every Browserbase tool action and event your agent gets out of the box.

Create a new browser context

Tool to create a new browser context.

Retrieve a browser context

Tool to retrieve details of a specific browser context.

Update Browser Context

Tool to update a specific browser context.

Create Browser Session

Tool to create a new browser session.

Delete a browser context

Tool to delete a browser context and all its stored data (cookies, localStorage, etc.

Delete a browser extension

Tool to delete an uploaded browser extension by its ID.

Delete Session Downloads

Tool to delete all file downloads from a specific browser session.

Retrieve a browser extension

Tool to retrieve details of a specific browser extension.

Retrieve a project

Tool to retrieve details of a specific project including settings and configuration.

Get project usage statistics

Tool to retrieve usage statistics for a project including browser minutes and proxy bytes consumed.

List Projects

Tool to list all projects for the authenticated account.

Retrieve a browser session

Tool to retrieve details of a specific browser session.

Retrieve Session Debug URLs

Tool to retrieve live debug URLs for a specific session.

Download Session Artifacts

Tool to download files from a specific session.

Retrieve Session Logs

Tool to retrieve logs of a specific session.

List Browser Sessions

Tool to list all browser sessions.

Update Browser Session

Tool to update the status of a specific browser session.

Upload Browser Extension

Tool to upload a browser extension for use in sessions.

Upload File to Session

Tool to upload files to a browser session for file input operations.

FAQ

Frequently asked questions

Yes. Muse supports custom connectors that use the Model Context Protocol (MCP). Composio connects as one custom connector over remote streamable HTTP at https://connect.composio.dev/mcp, and gives Muse access to Browserbase tool and 1,500+ other apps.

Copy it from the Composio dashboard. It starts with ck_. Enter it only in Muse's secure credentials store, never in the chat.

Yes. Composio supports multiple connected accounts for the same app. Give each Browserbase tool connection a name, such as work or personal, and tell Muse which one to use.

Tokens, keys, and configuration are encrypted at rest and in transit. Your Composio API key stays in Muse's secure credentials store, not in the chat or the model context. Composio is SOC 2 Type 2 compliant.

Start with Browserbase tool.It takes 30 seconds.

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

Start building