# How to connect Kernel MCP to Claude ```json { "title": "How to connect Kernel MCP to Claude", "toolkit": "Kernel MCP", "toolkit_slug": "kernel_mcp", "framework": "Claude Cowork", "framework_slug": "claude-cowork", "url": "https://composio.dev/toolkits/kernel_mcp/framework/claude-cowork", "markdown_url": "https://composio.dev/toolkits/kernel_mcp/framework/claude-cowork.md", "updated_at": "2026-09-02T05:39:40.420Z" } ``` ## 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 - [ChatGPT](https://composio.dev/toolkits/kernel_mcp/framework/chatgpt) - [Hermes](https://composio.dev/toolkits/kernel_mcp/framework/hermes-agent) ## Connect Kernel MCP to Claude Cowork ### 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](https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Composio&connectorUrl=https%3A%2F%2Fconnect.composio.dev%2Fmcp) ### Add manually In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top. Click Add custom connector and paste in the Composio MCP server URL: ```bash https://connect.composio.dev/mcp ``` ## What is the Kernel MCP server, 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. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `KERNEL_MCP_BROWSER_CURL` | Browser curl | Send an HTTP request through an existing Kernel browser session's Chrome network stack. Use when the request needs that browser session's cookies, proxy, network context, or origin behavior; do not use for general documentation lookup or web search. | | `KERNEL_MCP_COMPUTER_ACTION` | Computer action | Execute computer actions on a browser session. Pass a single action for simple operations (e.g. one click or one screenshot), or pass multiple actions to batch them into a single request for lower latency (e.g. click, type, press_key in one call). Use sleep actions between steps when the page needs time to react (e.g. after a click that triggers navigation or animation). IMPORTANT: Always include a screenshot as the last action so you can see the result of your actions. Action types: click_mouse, move_mouse, type_text, press_key, scroll, drag_mouse, set_cursor, sleep, write_clipboard, read_clipboard, screenshot, get_mouse_position. screenshot, read_clipboard, and get_mouse_position return data, so they must be the last action if included. | | `KERNEL_MCP_EXEC_COMMAND` | Exec command | Execute a command synchronously inside a browser VM. Returns stdout, stderr, and exit code. The command field is the executable; use args for its arguments. Common uses: read files (command: "cat", args: ["/var/log/supervisord.log"]), list dirs (command: "ls", args: ["/var/log"]), check DNS (command: "cat", args: ["/etc/resolv.conf"]), test connectivity (command: "curl", args: ["-I", "https://example.com"]). | | `KERNEL_MCP_EXECUTE_PLAYWRIGHT_CODE` | Execute playwright code | Execute Playwright/TypeScript automation code against an existing Kernel browser session. Does not create or delete browsers -- use manage_browsers to manage session lifecycle. | | `KERNEL_MCP_GET_CONNECTION_CONTEXT` | Get connection context | Inspect the authenticated Kernel connection before a project-scoped operation. connection_scope.kind=organization may omit project for organization-wide reads and default-project creates, or pass a project name or ID to select a project. connection_scope.kind=project is fixed to connection_scope.project_id; omit project or pass that project. | | `KERNEL_MCP_GET_MORE_TOOLS` | Get more tools | Check for additional tools whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback. | | `KERNEL_MCP_MANAGE_API_KEYS` | Manage api keys | Manage Kernel API keys. Use "create" to create an org-wide or project-scoped key, "list" to discover masked keys, "get" to retrieve one masked key, "update" to rename a key, or "delete" to revoke a key. Created keys include the plaintext key once. | | `KERNEL_MCP_MANAGE_APPS` | Manage apps | Manage Kernel apps when an agent needs to discover deployed app actions, invoke an app, or inspect deployment/invocation state. Use "list_apps" before invoking an unknown app. "invoke" starts an action asynchronously and returns an invocation_id immediately. Use "list_invocation_browsers" with that ID to discover browser sessions created by the invocation, and use "get_invocation" after a short delay to inspect its state. Do not poll indefinitely; if the invocation is still running, report its ID. Use get/list actions to inspect results and "delete_deployment" to remove a deployment. | | `KERNEL_MCP_MANAGE_AUTH_CONNECTIONS` | Manage auth connections | Manage reusable authenticated profiles for third-party websites. Before a browser task that needs a user account, call "list" with the exact domain_filter and inspect every page. If one relevant connection is AUTHENTICATED, create the browser with its profile_name. If multiple relevant accounts exist, ask the user which one to use. If authentication is needed and open_auth_login is available, prefer that secure App so credentials and MFA never enter chat: a direct user request to log in is already consent; if login is only discovered incidentally, ask first. For a new App login, choose a concise stable profile name derived from the service unless the user specified one. The programmatic actions remain available for every client: "create" a connection, "login" to start a hosted flow, "submit" fields/MFA/SSO, "get" status, "delete", or "wait" for completion. After authentication, resume the original task with manage_browsers using the verified profile_name. | | `KERNEL_MCP_MANAGE_BROWSER_POOLS` | Manage browser pools | Manage pre-warmed browser pools when an agent needs fast browser acquisition or reusable session capacity. Use "list" for a compact pool inventory, "get" for full details, "acquire" before controlling a pooled browser, and "release" when the browser should return to the pool. | | `KERNEL_MCP_MANAGE_BROWSERS` | Manage browsers | Manage browser sessions and their archived telemetry. Use "list" to choose an existing session, "create" before browser control, "update" to change supported session settings, "get" for full details, "get_telemetry" to diagnose active or deleted sessions, and "delete" when finished. get_telemetry compacts events by default; set compact=false with explicit categories and a limit of at most 5 when raw headers, request data, response bodies, or other omitted fields are needed. | | `KERNEL_MCP_MANAGE_CREDENTIAL_PROVIDERS` | Manage credential providers | Manage external credential providers (e.g. 1Password). "list" returns configured providers, "get" retrieves one by ID, "create" configures a new provider with a service-account token, "update" changes its name/token/priority/enabled/cache_ttl_seconds, "delete" removes it, "list_items" returns available credential items from the provider (e.g. 1Password login items with their paths), and "test" validates the token and lists accessible vaults. | | `KERNEL_MCP_MANAGE_CREDENTIALS` | Manage credentials | Manage credentials stored in Kernel for managed auth. "list" discovers credentials (optionally filtered by domain), "get" returns a credential's metadata (values are never returned), "totp_code" returns the current 6-digit TOTP for credentials with a configured totp_secret, "create" stores a new credential, "update" changes its name/values/sso_provider/totp_secret (values are merged with existing), and "delete" removes a credential by ID or name. | | `KERNEL_MCP_MANAGE_EXTENSIONS` | Manage extensions | Manage browser extensions uploaded to Kernel. Use "list" to see all extensions available to the current project or "delete" to remove one by ID or name. | | `KERNEL_MCP_MANAGE_PROFILES` | Manage profiles | Manage browser profiles when an agent needs persistent cookies, login state, or reusable browser state. Use "setup" for a guided login session, "list" to find a profile, "get" to retrieve one, "rename" to change its name, and "delete" only when a profile should be removed. Do not rename a profile while a browser is using it because that session may no longer save changes back to the profile. | | `KERNEL_MCP_MANAGE_PROJECTS` | Manage projects | Manage Kernel projects for resource isolation within an organization. Use "create" to create a project, "list" to discover projects, "get" to retrieve one, "update" to rename or archive one, "delete" to remove an empty project, "get_limits" to inspect project caps, or "update_limits" to change project caps. | | `KERNEL_MCP_MANAGE_PROXIES` | Manage proxies | Manage proxy configurations for routing browser traffic. Use "create" to add a proxy, "list" to see all proxies, "get" to retrieve one, "rename" to change its name, "check" to test connectivity (optionally against a target URL), or "delete" to remove one. Proxy quality for bot detection avoidance, best to worst: mobile > residential > ISP > datacenter. | | `KERNEL_MCP_MANAGE_REPLAYS` | Manage replays | Manage video replay recordings for a browser session. Use "start" to begin recording a session (returns a replay_id and a viewable URL), "stop" to end a recording and persist the video, or "list" to see all replays for a session with their view URLs. Recording is session-scoped: start once, run your automation, then stop -- rather than recording each action separately. Requires a paid Kernel plan; not available on the free tier. | | `KERNEL_MCP_SEARCH_DOCS` | Search docs | Search Kernel platform documentation for guides, tutorials, and API references. Use when you need to understand how Kernel features work or troubleshoot issues. | | `KERNEL_MCP_SUBMIT_FEEDBACK` | Submit feedback | send feedback about anything KERNEL to the KERNEL team. set `feedback_type` to route it: `product` for any KERNEL product or feature, `mcp` for this mcp server, `docs` for KERNEL documentation, or `other`. all sentiments are welcome through `sentiment`: praise and feature requests are useful, not just problems. use this for confusing or broken experiences, papercuts, missing capabilities, unhelpful errors, feature requests, and things that worked especially well. keep `summary` to one sentence and make the detail fields concise and actionable, quoting the product surface, tool name, parameter, or error text when possible. include a concrete `suggested_improvement` when one is clear. never include credentials, tokens, api keys, urls, browser or page content, customer or account names, or personal data. the user can also ask to send feedback directly. submitting feedback is a side report to KERNEL, not a reason to stop: continue and finish the user's task with the other available tools. | ## Supported Triggers None listed. ## 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. ## Creating MCP Server - Stand-alone vs Composio SDK The Kernel MCP server connects Claude Web, Desktop, and Cowork to your Kernel account through Composio. Once connected, Claude can use the available Kernel tools and triggers to complete tasks on your behalf. ## Complete Code None listed. ## How to build Kernel MCP Agent with another framework - [ChatGPT](https://composio.dev/toolkits/kernel_mcp/framework/chatgpt) - [Hermes](https://composio.dev/toolkits/kernel_mcp/framework/hermes-agent) ## Related Toolkits - [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure. - [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms. - [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place. - [1password](https://composio.dev/toolkits/_1password) - 1Password is a password manager and digital vault for storing logins, secrets, notes, and secure documents. It helps individuals and teams protect credentials, share access safely, and reduce password risk. - [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences. - [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses. - [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure. - [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure. - [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction. - [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting. - [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache. - [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence. - [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place. - [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines. - [Authyo](https://composio.dev/toolkits/authyo) - Authyo is a REST API service for passwordless authentication, OTP verification, session management, and transactional notifications. Use it to add secure login flows and user verification without building auth infrastructure from scratch. - [AWS Marketplace MCP](https://composio.dev/toolkits/aws_marketplace_mcp) - AWS Marketplace MCP provides MCP access to AWS Marketplace's cloud software, data, and services catalog. Use it to discover, compare, and evaluate 30K+ AWS Marketplace listings faster. - [Azure Monitor Activity Log](https://composio.dev/toolkits/azure_monitor_activity_log) - Azure Monitor Activity Log is Azure's service that records management and control-plane events for a subscription. Use it to audit changes, troubleshoot issues, and track resource operations across your Azure resources. - [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure. - [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code. - [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Kernel MCP? 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. ### Can I use Tool Router MCP with Claude Cowork? 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. ### Can I manage the permissions and scopes for Kernel while using Tool Router? 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. ### How safe is my data with Composio Tool Router? 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. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)