Kernel MCP server for AI agents and assistants

Securely connect your AI agents and chatbots (Claude, ChatGPT, Cursor, etc) with Kernel MCP or direct API to launch cloud browsers, run Playwright tasks, control computers, and manage persistent browser profiles through natural language.

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

Try Kernel now

Type what you want done — sign in and watch it run live in the Tool Router playground.

TOOL ROUTER PLAYGROUND
Kernel
Try asking
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.

SETUP GUIDE

Connect Kernel MCP Tool with your Agent

1

Install Composio

typescript
npm install @composio/core ai @ai-sdk/mcp @ai-sdk/openai
Install the Composio SDK and your agent framework
2

Create a session with MCP enabled

typescript
import { Composio } from "@composio/core";

const composio = new Composio();
const { mcp } = await composio.create("your-user-id", {
  toolkits: ["kernel"],
  mcp: true,
});
Create a session scoped to Kernel and read its MCP URL and headers
3

Connect your agent to the MCP server

typescript
import { createMCPClient } from "@ai-sdk/mcp";
import { openai } from "@ai-sdk/openai";
import { generateText, stepCountIs } from "ai";

const client = await createMCPClient({
  transport: { type: "http", url: mcp.url, headers: mcp.headers },
});

const { text } = await generateText({
  model: openai("gpt-5.6-sol"),
  tools: await client.tools(),
  prompt: "Launch a Kernel cloud browser, open https://example.com, and return the page title.",
  stopWhen: stepCountIs(10),
});

console.log(text);
await client.close();
Pass the session's MCP URL and headers to your agent and run a Kernel request
SETUP GUIDE

Connect Kernel API Tool with your Agent

1

Install Composio

typescript
npm install @composio/core @composio/openai openai
Install the Composio SDK, the OpenAI provider, and the OpenAI SDK
2

Create a Composio session

typescript
import OpenAI from "openai";
import { Composio } from "@composio/core";
import { OpenAIResponsesProvider } from "@composio/openai";

const composio = new Composio({ provider: new OpenAIResponsesProvider() });
const client = new OpenAI();

const session = await composio.create("your-user-id", { toolkits: ["kernel"] });
const tools = await session.tools();
Initialize Composio with the OpenAI Responses provider and create a session scoped to Kernel
3

Run Kernel tools with your agent

typescript
let response = await client.responses.create({
  model: "gpt-5.6-sol",
  tools,
  input: [{ role: "user", content: "Launch a Kernel cloud browser, open https://example.com, and return the page title." }],
});

while (response.output.some((o) => o.type === "function_call")) {
  const outputs = await composio.provider.handleToolCalls(session, response.output);
  response = await client.responses.create({
    model: "gpt-5.6-sol",
    tools,
    previous_response_id: response.id,
    input: outputs,
  });
}

console.log(response.output_text);
Send a request, execute the Kernel tool calls through the session, and print the final answer

Why Use Composio?

AI Native Kernel Integration

  • Supports both Kernel MCP and direct API based integrations
  • Structured, LLM-friendly schemas for reliable browser and automation tool execution
  • Rich coverage for cloud browsers, Playwright runs, computer controls, session replays, and persistent profiles

Managed Auth

  • Securely store and use your Kernel API key without hard-coding it into agent code
  • Central place to manage, scope, and revoke Kernel access
  • Per user and per environment credentials for safer browser automation

Agent Optimized Design

  • Tools are tuned using real error and success rates to improve browser task reliability over time
  • Comprehensive execution logs so you always know what ran, when, and on whose behalf

Enterprise Grade Security

  • Fine-grained RBAC so you control which agents and users can access Kernel
  • Scoped, least privilege access to browser sessions, profiles, and automation resources
  • Full audit trail of agent actions to support review and compliance

Rolling this out across your team?

Give your team centralized access control across every framework with Composio’s MCP Gateway.

EXPLORE MCP GATEWAY
FAQ

Frequently asked questions

Yes, Kernel requires you to configure your own API key. Once set up, Composio handles secure credential storage and API request handling for you.

Yes! Composio's Tool Router enables agents to use multiple toolkits. Learn more.

Yes. Composio is SOC 2 Type II compliant and is built to keep your Kernel connection and credentials secure. OAuth tokens and API keys are encrypted, and sensitive customer data is protected at rest and in transit.

Composio also undergoes independent security testing and continuously monitors its systems for security threats. You can review the latest reports and policies in the Composio Trust Center.

Composio maintains and updates all toolkit integrations automatically, so your agents always work with the latest API versions.

Create the key in your Kernel account settings, then paste it once on Composio's connection page. Composio stores it encrypted and uses it only for the Kernel actions your agent runs. Nobody else in your workspace can read it, and you can revoke it inside Kernel at any time.

When you connect a Kernel account through Composio, every action runs under that account, so anything the agent creates, sends, or changes shows up in Kernel as done by you. Keep an approval step in your prompt for actions with side effects, such as sending or deleting, and have the agent draft first.

Whatever the credentials you connect allow inside Kernel. If Kernel lets you scope a key to specific permissions, create a scoped one so the agent can only do what you intend. You can revoke the key inside Kernel at any time.

Yes. Composio supports multiple connected accounts for the same app, and that works in Claude, ChatGPT, or any other assistant you connect through Composio. Give each Kernel connection a name such as work or personal, and the assistant uses the one you mention in the request. Each account keeps its own credentials and nothing is merged.

The connection stops working the moment Kernel rejects the old key. Create a new key in Kernel and reconnect the account from the Composio dashboard or by asking your agent to reconnect Kernel. Nothing else changes.

Composio's free Hobby plan includes 100,000 tool calls per month with no credit card, which covers most personal Kernel use. Paid plans add higher limits and team features. Your Kernel plan and its API limits still apply as usual.

Built-in connectors usually give one AI access to a limited set of apps. Many people use Composio because it lets their AI connect to more apps than it normally supports, or connect to multiple accounts for the same app (e.g. connect Claude to multiple Kernel accounts).

With Composio, you connect Kernel once and then use it across different AI assistants without setting it up separately in each one. Connect your apps to Composio once, then connect Composio to whichever AI you use, whether that's Claude, ChatGPT, Hermes, or your own custom assistant.

Start with Kernel.It takes 30 seconds.

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

Start building