[ MCP SERVER SUMMARY ]
Kernel MCP server summary
Kernel's hosted MCP server gives AI assistants cloud browser infrastructure — launch Chromium sessions, run Playwright against live browsers, deploy Kernel apps, and review replays. Bifrost fronts the remote endpoint so browser automation is policy-controlled and auditable.
| Property | Details |
|---|---|
| Company | Kernel |
| Connection type | HTTP |
| Authentication | OAuth 2.1 (Clerk) |
| Package or endpoint | https://mcp.onkernel.com/mcp |
| Capabilities | Cloud browser sessions, Playwright in the cloud, App deploy and invocation monitoring |
| Official documentation | Kernel MCP documentation |
Before you start
- A Kernel account
- OAuth-capable MCP client configuration in Bifrost
What you can do with Kernel
- Run browser automation without managing local Chromium on every agent host
- Share one Kernel OAuth connection across Cursor and Claude Code via Bifrost
- Limit which Kernel browser tools non-prod keys can invoke
[ HOW TO CONNECT ]
Connect Kernel to Bifrost in three steps
Install Bifrost
Start the gateway locally or deploy in your VPC.
npx -y @maximhq/bifrost
Add Kernel in MCP Gateway
Open MCP Gateway in the Bifrost dashboard, click New MCP Server, and choose HTTP. Or register via the API below.
• Streamable HTTP endpoint: https://mcp.onkernel.com/mcp.
• Clients without remote MCP can use npx mcp-remote as a STDIO bridge to the same URL.
Point clients at Bifrost /mcp
Configure Claude Desktop, Cursor, or Claude Code to use your Bifrost endpoint with a virtual key instead of connecting directly to Kernel.
{
"mcpServers": {
"bifrost": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer vk_your_virtual_key"
}
}
}
}[ EXAMPLE CONFIG ]
Register Kernel via API
Add this MCP client with a POST to /api/mcp/client. See Connecting to MCP Servers for full options.
curl -X POST http://localhost:8080/api/mcp/client \
-H "Content-Type: application/json" \
-d '{
"name": "kernel",
"connection_type": "http",
"connection_string": "https://mcp.onkernel.com/mcp",
"auth_type": "oauth",
"tools_to_execute": [
"*"
]
}'[ WHY BIFROST ]
Run Kernel through one governed gateway
Access control
Virtual keys, RBAC, and tool allowlists per team or agent.
Cost governance
Attribute MCP tool spend alongside LLM usage in one view.
Observability
Log every tool call with latency, server, and virtual key metadata.
Credential isolation
Upstream secrets stay in the gateway — not on every laptop.
[ FAQ ]
Common questions
What does the Kernel MCP server do?
Kernel exposes cloud browser sessions, playwright in the cloud, app deploy and invocation monitoring to MCP-compatible AI clients. Bifrost connects to it as an upstream MCP client and exposes approved tools through one governed /mcp endpoint.
How does Kernel authenticate when used with Bifrost?
Kernel uses OAuth 2.1 (Clerk). Store credentials in Bifrost's environment or credential configuration so they stay at the gateway instead of being copied into every AI client.
Can Claude Desktop, Cursor, or Claude Code use Kernel through Bifrost?
Yes. After registering Kernel in Bifrost, point any HTTP MCP-compatible client at the Bifrost /mcp endpoint and authenticate with a virtual key. The client sees only the tools allowed for that key.
[ RELATED SERVERS ]
More MCP integrations
Playwright
Microsoft’s official browser automation MCP server for navigating pages, interacting with web apps, and running browser-based workflows.
Sentry
Use Sentry’s MCP server to investigate errors, issues, traces, and application health from AI coding assistants.
Context7
Provide AI coding assistants with current, version-specific library documentation and code examples through Context7.