Get started

Kernel for AI agents

Kernel gives agents access to cloud-hosted browsers and browser automation infrastructure for running scripted web tasks. Engineering teams pull it into internal tools and scripts rather than building the same capability themselves. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect KernelSee the 25 actions ↓
Developer toolsOAuth 2.0 (MCP)MCP + RESTonkernel.com
AUDIT LOG · KERNELPOLICY: acme-support
09:41:07 · claude · u_8f2read
kernel.search_docs
Search docs✓ allowed · 212ms
09:41:08 · claude · u_8f2read
kernel.get_more_tools
Get more tools✓ allowed · 164ms
09:41:09 · claude · u_8f2write
kernel.webmcp
Webmcp✓ approved · approved by user
EVERY KERNEL CALL, ON THE RECORD
01 · USE CASES

What agents do in Kernel.

01

Run a browser automation task

Execute a scripted browser action against a target site to complete a repetitive web task.

02

Check a browser session's status

Check the status of a running cloud browser session before sending it a new command.

03

Manage credentials with approval

Store or update a stored credential in the vault only after the user explicitly confirms it.

02 · ACTIONS

25 Kernel actions, graded by risk.

Every Kernel action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

3

Look things up. Allowed by default.

  • kernel.search_docs
    Search docs
  • kernel.get_more_tools
    Get more tools
  • kernel.get_connection_context
    Get connection context

write

22

Create and change things. Allow, or ask the user first.

  • kernel.webmcp
    Webmcp
  • kernel.manage_apps
    Manage apps
  • kernel.browser_curl
    Browser curl
  • kernel.exec_command
    Exec command
  • kernel.manage_vaults
    Manage vaults
  • kernel.manage_proxies
    Manage proxies
  • kernel.manage_replays
    Manage replays
  • kernel.computer_action
    Computer action
  • kernel.manage_api_keys
    Manage api keys
  • kernel.manage_browsers
    Manage browsers
  • kernel.manage_profiles
    Manage profiles
  • kernel.manage_projects
    Manage projects
  • kernel.submit_feedback
    Submit feedback
  • kernel.manage_extensions
    Manage extensions
  • kernel.manage_credentials
    Manage credentials
  • kernel.manage_vault_cards
    Manage vault cards
+ 6 MORE

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · HOW IT WORKS

Kernel in three steps.

  1. 01Your users connect KernelThey sign in to Kernel on Arc0 Connect, under your brand, and approve the access you ask for.
  2. 02You set the rulesReads run, and writes like “webmcp” can wait for the user to approve.
  3. 03Any agent can actYour agent calls Kernel through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('kernel', {
  read: 'allow',
  write: 'ask',        // webmcp
  destructive: 'deny',  
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Kernel connects.

Kernel runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches Kernel through the same endpoint, policies and audit log as every other app.

The same Kernel connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
OAuth 2.0 (MCP)
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Kernel from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More developer tools apps.

GitHub896 actionsSupabase129 actions0CodeKit8 actionsAbly25 actionsAbstract3 actionsAddressfinder17 actionsAddresszen2 actionsAlchemy36 actions
ALL DEVELOPER TOOLS APPS →
07 · FAQ

Kernel and Arc0, answered.

Q01

Can I use Kernel with Claude, ChatGPT or Cursor?

Yes. Connect Kernel to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Kernel actions you allow.

Q02

How do users connect Kernel?

Kernel runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches Kernel through the same endpoint, policies and audit log as every other app.

Q03

Which Kernel actions can my agent take?

25 in total: 3 read, 22 write and 0 destructive, such as “webmcp”. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in Kernel?

Yes. Allow read actions and deny writes in the Kernel policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call Kernel too?

Yes. The same Kernel connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Kernel into your agent.

Your users connect Kernel once, under your brand. Your agent gets 25 actions behind your policies, with every call on the record.

Connect KernelBrowse all apps →

Free to build · MCP + REST · Audit log on every plan