How to connect Kernel to Claude

Connect Claude Web, Desktop and Cowork to Kernel MCP. Launch a cloud browser for checkout testing, run playwright checks on a web app, and more using natural language, with authentication handled for you.

Kernel logoKernel
Api Key

Kernel is a browser automation platform with cloud browsers, computer controls, Playwright execution, and session replays. It provides persistent browser profiles and reliable infrastructure for browser-based workflows.

35 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 Kernel account to Claude via Composio Connect, enabling it to launch a cloud browser for checkout testing, run Playwright checks on a web app, review a browser session replay, 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 Kernel with

Connecting Kernel 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 Kernel account

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

For example, ask Claude to:

  • "Launch a cloud browser for checkout testing"
  • "Run Playwright checks on a web app"
  • "Review a browser session replay"

It will prompt you to authenticate and authorize access.

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

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

The Kernel MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Kernel account. It provides structured and secure access to cloud browsers, persistent profiles, computer controls, Playwright execution, browser network requests, screenshots, and session replays, so your agent can create browser sessions, interact with websites, run Playwright workflows, preserve browser state, and record sessions on your behalf.

  • Cloud browser control: Have your agent create, update, inspect, and delete browser sessions, then click, scroll, type text, press keys, move the mouse, and capture screenshots.
  • Playwright browser automation: Direct your agent to run JavaScript or TypeScript with Playwright to navigate pages, interact with forms, submit actions, and automate browser workflows.
  • Persistent browser profiles: Let the agent create, save, download, rename, list, and delete browser profiles so browser state can be reused across sessions.
  • Authenticated browser requests: Instruct your agent to send read-only or state-changing HTTP requests through a browser while using its cookies, headers, TLS fingerprint, and proxy settings.
  • Session recording and extensions: Have your agent start and stop browser replays, list and retrieve recordings, and upload unpacked Chromium extensions to a running browser.

Troubleshooting

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

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

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

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

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

  • 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 Kernel.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Kernel authorization link not work?

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

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

4. Why do Kernel actions fail after they worked before?

The Kernel connection can expire or lose permission.

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

5. How do I switch to a different Kernel account?

Claude can manage the Kernel connection for you.

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

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

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

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Kernel 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 Kernel.
TOOLS

Supported Tools

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

Batch Computer Actions

Execute 1-100 computer actions sequentially in a Kernel browser, stopping on the first error.

Browser Curl

Send a read-only GET, HEAD, or OPTIONS request through a Kernel browser's network stack, inheriting its cookies, TLS fingerprint, proxy settings, and default headers.

Browser HTTP Request

Send a state-changing POST, PUT, PATCH, or DELETE request through a Kernel browser's network stack, inheriting its cookies, TLS fingerprint, proxy settings, and default headers.

Click

Click at browser viewport coordinates with an optional mouse button, click phase, modifiers, and repetition count.

Create Browser

Create a Kernel browser session; defaults to a headless browser with a 60-second inactivity timeout.

Create Profile

Create an empty persistent browser profile, optionally with a unique name, for reuse by later browser sessions.

Delete Browser

Permanently end and delete a Kernel browser session by ID or name.

Delete Playwright Executor

Stop and permanently delete a named, non-default Playwright executor from a Kernel browser.

Delete Profile

Permanently delete a browser profile by ID or name.

Download Profile

Download a profile's stored browser state.

Drag Mouse

Drag a mouse button through an ordered path of browser viewport coordinates, with optional timing, linear-step, and modifier controls.

Execute Playwright

Execute arbitrary TypeScript or JavaScript with Playwright access to the browser; the code may navigate, mutate pages, submit forms, or cause irreversible external effects.

Get Browser

Get safe operational details for one browser session by ID or name, optionally including a deleted session.

Get Mouse Position

Get the current mouse cursor coordinates in a Kernel browser session.

Get Profile

Get one browser profile by its ID or exact name.

Get Replay

Download a completed browser replay as MP4.

List Browsers

List browser sessions, optionally filtered by lifecycle state, search text, tags, or region, one offset page at a time.

List Playwright Executors

List the default and named Playwright executors for a Kernel browser, including whether each is busy and its owned tab when available.

List Profiles

List browser profiles, optionally filtered by substring or exact name, one offset page at a time.

List Replays

List replay recordings for a headful browser session without returning signed viewer URLs.

Move Mouse

Move the cursor to browser viewport coordinates, optionally using a timed human-like path and held modifier keys.

Press Key

Press an ordered sequence of X11 keys or key chords in a browser, optionally holding modifiers or holding the sequence for a duration.

Read Clipboard

Read the current text from a Kernel browser session's clipboard.

Rename Profile

Rename a Kernel browser profile by ID or exact name.

Restart Default Playwright Executor

Restart a Kernel browser's reserved default Playwright executor.

Save Browser Profile

Save a running browser's current state to exactly one destination profile ID or name, creating a named profile when needed and overwriting an existing destination.

Scroll

Scroll horizontally or vertically at browser viewport coordinates, optionally while holding modifier keys.

Set Cursor Visibility

Hide or show the cursor in a Kernel browser session.

Start Replay

Start recording a headful Kernel browser session and return its replay identifier and recording metadata without exposing its signed viewer URL.

Stop Replay

Stop an active replay recording for a Kernel browser identified by ID or name.

Take Screenshot

Capture the full browser viewport or a rectangular region as a PNG download.

Type Text

Type text into the currently focused browser element with an optional per-keystroke delay.

Update Browser

Update mutable settings on an existing Kernel browser session.

Upload Browser Extensions

Upload and activate one or more unpacked Chromium extension ZIP archives in an existing running browser.

Write Clipboard

Write text to the system clipboard of a Kernel browser session.

FAQ

Frequently asked questions

With a standalone Kernel MCP server, the agents and LLMs can only access a fixed set of Kernel tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Kernel 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 Kernel tools.

Yes, absolutely. You can configure which Kernel 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 Kernel data and credentials are handled as safely as possible.

Start with Kernel.It takes 30 seconds.

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

Start building