How to connect Kernel MCP to Claude

Connect Claude Web, Desktop and Cowork to Kernel MCP. Take a full-page screenshot of dashboard, login and export account activity csv, and more using natural language, with authentication handled for you.

Kernel MCP logoKernel MCP
Dcr Oauth

Kernel MCP is a cloud-browser infrastructure and browser automation platform with a hosted OAuth server. Use it to run reliable remote browsing sessions and automate web tasks without managing browsers.

20 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 take a full-page screenshot of dashboard, login and export account activity CSV, fill signup form and submit confirmation, 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 MCP 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:

  • "Take a full-page screenshot of dashboard"
  • "Login and export account activity CSV"
  • "Fill signup form and submit confirmation"

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 so your agent can perform Kernel operations on your behalf.

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 MCP action and event your agent gets out of the box.

Browser curl

Send an HTTP request through an existing Kernel browser session's Chrome network stack.

Computer action

Execute computer actions on a browser session.

Exec command

Execute a command synchronously inside a browser VM.

Execute playwright code

Execute Playwright/TypeScript automation code against an existing Kernel browser session.

Get connection context

Inspect the authenticated Kernel connection before a project-scoped operation.

Get more tools

Check for additional tools whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback.

Manage api keys

Manage Kernel API keys.

Manage apps

Manage Kernel apps when an agent needs to discover deployed app actions, invoke an app, or inspect deployment/invocation state.

Manage auth connections

Manage reusable authenticated profiles for third-party websites.

Manage browser pools

Manage pre-warmed browser pools when an agent needs fast browser acquisition or reusable session capacity.

Manage browsers

Manage browser sessions and their archived telemetry.

Manage credential providers

Manage external credential providers (e.

Manage credentials

Manage credentials stored in Kernel for managed auth.

Manage extensions

Manage browser extensions uploaded to Kernel.

Manage profiles

Manage browser profiles when an agent needs persistent cookies, login state, or reusable browser state.

Manage projects

Manage Kernel projects for resource isolation within an organization.

Manage proxies

Manage proxy configurations for routing browser traffic.

Manage replays

Manage video replay recordings for a browser session.

Search docs

Search Kernel platform documentation for guides, tutorials, and API references.

Submit feedback

send feedback about anything KERNEL to the KERNEL team.

FRAMEWORKS

How to build Kernel MCP Agent with another framework

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 MCP.It takes 30 seconds.

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

Start building