kernel-mcp-server
Kernel MCP Server is a hosted Model Context Protocol (MCP) server that lets MCP-compatible clients securely access the Kernel platform, including deploying/managing Kernel apps and controlling cloud headless Chromium sessions for browser automation. It supports Streamable HTTP (recommended) and stdio via mcp-remote, with OAuth2.1 authentication handled via Clerk.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Uses OAuth 2.1 via Clerk for the remote hosted MCP endpoint. The README emphasizes authentication but does not document fine-grained scopes/permissions per tool. No information is provided about TLS enforcement details, rate limiting, audit logs, or how credentials/tokens are handled in responses/errors.
⚡ Reliability
Best When
You want an agent-friendly, remote MCP endpoint that provides cloud browser automation and app execution with a single consistent tool surface.
Avoid When
You require fine-grained control over browser/network execution at the client side (since execution occurs on the Kernel-hosted infrastructure) or you cannot use OAuth-based connector authorization flows.
Use Cases
- • Deploy and invoke Kernel apps from AI agents/tooling
- • Headless Chromium browser automation (e.g., navigate, click, type, screenshot) via MCP tools
- • Run dynamic Playwright/TypeScript against live browser sessions (with replay video recording)
- • Create and manage persistent browser profiles (cookies/logins) for automation workflows
- • Use pre-warmed browser pools and proxies for scalable automation
- • Search Kernel documentation and inject context into agent workflows
- • Debug and troubleshoot browser sessions using provided prompts
Not For
- • Offline/local-only browser automation without network access to the hosted MCP endpoint
- • Use cases requiring no authentication/anonymous access
- • Highly regulated environments where data residency/compliance details are not provided
Interface
Authentication
README indicates OAuth2.1 authentication via Clerk for the centrally hosted remote MCP server. It does not describe specific OAuth scopes or how they map to MCP tool permissions.
Pricing
No pricing details were provided in the supplied README/repo metadata.
Agent Metadata
Known Gotchas
- ⚠ OAuth/connector setup may require different steps depending on client (e.g., Claude free vs Pro/Team).
- ⚠ Cursor clean reset involves clearing all MCP tokens; stale auth can require removing saved tokens (e.g., ~/.mcp-auth).
- ⚠ HTTP remote MCP is recommended, but some clients may require stdio via npx -y mcp-remote.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for kernel-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.