Developer Tools & Devops · Kernel MCP + Claude
Kernel MCP with Claude: Automate Web Tasks Without Managing Browsers
The short answer
Claude works with Kernel through the Model Context Protocol (MCP). Kernel provides a hosted MCP server that lets Claude start cloud browser sessions, browse pages, fill forms, capture screenshots and run page scripts. Access is granted through a dynamic client registration OAuth sign-in, so the organisation controls what Claude can do.
What is Kernel MCP?
Kernel is a cloud browser infrastructure and browser automation platform. It runs remote browsing sessions on hosted infrastructure, so teams do not have to install, maintain or scale browsers themselves. It also offers a hosted OAuth server for secure sign-in. Developers, operations teams and product teams typically use it to automate repetitive web tasks, such as checking portals, gathering information from websites and completing online forms.
How Claude connects to Kernel MCP through MCP
The Model Context Protocol is an open standard that lets Claude securely use other software, reading information and taking actions, with permissions the organisation controls. Think of it as a universal adapter between Claude and the tool. Kernel publishes an MCP server, so Claude can reach its browser capabilities through that adapter.
Once connected, Claude can typically start a remote browser session, open web pages, read what is on them, fill in forms, capture screenshots and run page scripts when you describe the task in plain language. The work happens on Kernel's cloud browsers rather than on your staff's computers, which keeps routine web tasks running reliably in the background.
Permissions and approvals keep people in charge. Access is granted through dynamic client registration OAuth, so each connection is authorised by a person and can be limited to the actions that make sense for the job. Sensitive steps, such as submitting payments or changing account details, can be set to require a person's approval before Claude proceeds.
What you can automate
Portal status checks
An operations team needs to check the status of shipments or orders on several supplier portals each morning. Claude can open each portal in a remote browser session, read the current status and summarise any exceptions. Staff receive one consolidated list instead of logging into every site by hand.
Online form filling
A finance or administration team regularly submits the same details to government, bank or vendor websites. Claude can fill in those forms from approved data and capture a screenshot as a record of each submission. A person reviews the completed form before final submission, so accuracy stays under human control.
Competitor and price monitoring
A commercial team wants to track prices and product listings on public websites. Claude can visit the pages on a schedule, extract the relevant figures and flag meaningful changes. The output can be shared as a short weekly brief, saving analysts hours of manual checking.
Evidence capture for compliance
A compliance or audit team must keep proof that certain web pages showed particular content on specific dates. Claude can visit those pages and capture screenshots with timestamps, filed into a shared folder. This creates a consistent evidence trail without manual screenshots.
Website testing support
A digital team needs to confirm that key pages still load and that forms still work after each release. Claude can run through these checks in a remote browser and report any pages that fail. Developers spend less time on repetitive checks and more time on fixes.
An end-to-end workflow: Supplier onboarding and records update
TriggerA new supplier is approved in the CRM and marked ready for registration on a government or partner portal.
Claude reads the approved supplier details from the CRM.
Claude opens the partner portal in a Kernel cloud browser session and signs in using the approved access.
Claude fills in the registration form with the supplier details and captures a screenshot of the completed form.
A procurement officer reviews the form and the screenshot, then approves the final submission.
Claude records the confirmation reference and screenshot back to the CRM and posts a summary to the team's chat channel.
OutcomeSupplier registration is completed faster and with fewer keying errors, with a screenshot kept on file for audit. Typical teams report that onboarding steps which once took most of a day can be completed in a fraction of that time, with people still approving each submission.
How we set it up
Free automation audit
We review your current web-based tasks with your operations and IT leads and identify the workflows worth automating. You receive a clear list of candidates ranked by time saved and risk.
Secure connection
We connect Claude to Kernel through its hosted MCP server using dynamic client registration OAuth. Access is granted by an authorised person, with least-privilege permissions limited to the actions each workflow needs.
Workflow design
We design the end-to-end workflow across Kernel and your other systems, such as Microsoft 365, your CRM or ticketing tool. Approval points are set for any consequential action, such as submissions or changes to records.
Testing against real cases
We test the workflow against past real examples to confirm accuracy and handling of edge cases, such as unexpected page layouts or timeouts. We adjust the workflow until results meet agreed standards.
Launch, monitoring and training
We launch with monitoring and audit logs, then train your team on how to start tasks, review outputs and handle exceptions. Support continues while the workflow settles into daily use.
Who benefits
- Operations managers
- Routine portal checks and form submissions run reliably in the background, freeing the team for exceptions and decisions.
- IT and DevOps leads
- Browser infrastructure is hosted rather than maintained in-house, with OAuth-based access that IT can review and revoke.
- Finance and compliance teams
- Screenshots and records of web activity are captured consistently, creating a clear evidence trail for audits.
- Digital and product teams
- Repetitive website checks run automatically, so issues are spotted sooner and developers focus on building.
Security and control
- Access is granted through dynamic client registration OAuth, so each connection is authorised by a person and can be withdrawn.
- Permissions are limited to the minimum each workflow needs, reducing what Claude can reach.
- Consequential actions such as final submissions or payments can require human approval before they proceed.
- Audit logs and screenshots record what was done, supporting review and accountability.
- Only sites your organisation is permitted to access and automate should be included in any workflow.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can design these workflows to align with their own data protection and security requirements. In India, workflows are designed with the Digital Personal Data Protection Act, 2023 in mind, including how personal data appears on the pages Claude visits. Organisations in the UAE and Saudi Arabia can align with local data protection laws. Claude can be hosted in India, the United States, the United Kingdom or the European Union, and the hosting region is chosen to meet your legal and contractual requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Kernel MCP server do?
The Kernel MCP server is a hosted bridge that lets Claude use Kernel's cloud browsers. Through it, Claude can start browsing sessions, open web pages, fill forms, capture screenshots and run page scripts when asked in plain language. You do not need to install or run browsers yourself.
Is Kernel MCP secure?
Security depends on how the connection is set up. Kernel offers a hosted OAuth server with dynamic client registration, so access is authorised by a person. We typically add least-privilege permissions, approval steps for sensitive actions and audit logs to keep control with your organisation.
What can Claude do with Kernel?
Once connected, Claude can typically browse websites, read page content, fill in forms, capture screenshots and run page scripts in a remote browser session. The exact actions available depend on how the connection and workflow are configured for your organisation.
How long does setup take?
Setup time varies with the number and complexity of workflows. A simple single-site task can often be connected and tested within a few days, while multi-system workflows with approvals and training usually take several weeks. Your free automation audit gives you a realistic timeline.
Which plan or permissions do I need for Kernel MCP?
Generally, you need an active Kernel account and the ability to authorise a connection through its OAuth sign-in. The specific plan and permission levels depend on your Kernel account and the usage your workflows require, so we confirm these during the audit.