@kernline/mcp
Provides access to CSS inspection output from browser tabs where the Kernline panel is open, allowing MCP clients to read style information exposed by the extension.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@kernline/mcp get the Tailwind classes for the selected component"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@kernline/mcp
Local MCP server for the Kernline browser extension. It lets Cursor, Claude Desktop and other MCP clients read inspection output (CSS, Tailwind, design tokens, Copy for AI bundles) from tabs where the Kernline panel is open.
Public source for this package is the read-only mirror devson-software/kernline-mcp. Kernline copies this folder there on push. Do not edit the mirror.
Everything stays on your computer. The server listens on 127.0.0.1 only, accepts connections from the Kernline extension only, and proves itself with a pairing token before any data is shared. Kernline never receives page content on its servers. Your AI app may send what it reads to its own model provider.
Setup
In Kernline, open Settings, go to MCP server, tick Enable MCP server, then click Copy token.
Add the server to your MCP client with that token.
Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"kernline": {
"command": "npx",
"args": ["-y", "@kernline/mcp"],
"env": { "KERNLINE_BRIDGE_TOKEN": "paste-your-token" }
}
}
}Claude Desktop (claude_desktop_config.json)
Use the same kernline block under mcpServers.
Open the Kernline panel on a tab, then ask your AI app to use the Kernline tools.
Related MCP server: MultiZen
Options
KERNLINE_BRIDGE_TOKEN(required) is the pairing token from Kernline settings.KERNLINE_BRIDGE_PORT(optional, default47321) must match the port in Kernline settings.
Requires Node.js 18 or newer. Pro tools (Copy for AI, page tokens) need a Kernline Pro licence in the extension.
License
MIT, made by Devson Software in South Africa. The Kernline browser extension itself is not open source.
Available Tools
10 toolskernline_assetARead-only
Fetch one asset by id from kernline_assets (inline SVG or text, size-capped)
Inputs: id (required), tabId.
kernline_assetsARead-only
List page assets discovered by Kernline (images, SVG, fonts, favicons)
Inputs: tabId.
kernline_component_captureBRead-only
Pro: component tree capture as html, react, or vue with Tailwind classes
Inputs: tabId, format.
kernline_copy_for_aiARead-only
Pro: copy-for-AI bundle (HTML, computed CSS, tokens, sizes, states) for the pinned element
Inputs: tabId.
kernline_element_imageARead-only
PNG screenshot crop of the pinned element or selector (requires Kernline open on tab)
Inputs: tabId, selector.
kernline_inspectARead-only
Computed style snapshot, cleaned CSS, and Tailwind classes for the pinned element or a CSS selector
Inputs: tabId, selector.
kernline_list_tabsARead-only
List browser tabs where Kernline is open and connected to the local bridge
Inputs: no named parameters.
kernline_page_summaryCRead-only
Viewport, frames, and blocked stylesheet origins for an inspected tab
Inputs: tabId.
kernline_page_tokensCRead-only
Pro: scan page design tokens (css variables, tailwind v3/v4, json, or AI context)
Inputs: tabId, format.
kernline_pinB
Scroll a selector into view and pin it in Kernline so the user sees what was selected
Inputs: selector (required), tabId.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Most tools have clearly distinct purposes: tab listing, page summary, asset listing/fetching, screenshot capture, and pinning are well separated. The main ambiguity is among inspect, copy_for_ai, component_capture, and element_image, which all operate on a pinned element or selector, though their output formats are described differently.
All tools use a consistent kernline_ prefix and snake_case naming, making the set easy to scan. However, the naming mixes verbs and nouns (e.g., kernline_inspect, kernline_pin vs. kernline_page_summary, kernline_assets) rather than following a strict verb_noun pattern.
Ten tools is well-scoped for a browser/design inspection bridge, falling comfortably within the typical 3-15 range. Each tool appears to cover a distinct inspection or capture capability without excessive surface area.
The surface covers the core lifecycle well: listing tabs, inspecting pages/elements, capturing styles/components/tokens, listing and fetching assets, screenshotting, and pinning elements. Minor gaps exist, such as no explicit unpin/clear-selection operation and limited asset fetching for binary files, but these are likely workable.
Maintenance
Related MCP Connectors
Serves your design system and coding standards to coding agents, so they stop guessing.
Shared memory MCP server for Claude Code, Codex, Gemini CLI and Cursor. Cited, editable.
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
Live browser debugging for AI assistants — DOM, console, network via MCP.
Related MCP Servers
- FlicenseAqualityBmaintenanceLets an AI share the same live browser tab as a person, receiving the user's Alt+click target and enabling the AI to inspect, click, fill, type, navigate, or otherwise operate on that real page. It runs locally and pairs with the browser extension to bridge the user's page to the MCP client.13-
- FlicenseNot gradedqualityAmaintenanceExposes a localhost MCP endpoint that lets AI agents drive isolated browser profiles — navigating, clicking, typing, extracting, screenshotting, evaluating JS, and managing tabs and cookies — so real authenticated workflows can be completed from MCP clients like Cursor or Claude Desktop. Cookies, login state, fingerprints, and proxies persist per profile across launches and AI sessions.-
- FlicenseNot gradedqualityAmaintenanceConnects web-based AI chat clients such as Claude, ChatGPT, and Grok to a local machine through a single OAuth-gated MCP endpoint so they can browse, read, write, and edit files, run whitelisted shell commands, search content, use Git, query SQLite, drive browsers and DevTools, and manage background tasks, ports, and clipboard. It also exposes localhost and LAN services via a protected HTTP client, letting remote or mobile clients debug and operate local projects without granting unrestricted shell access.-
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding tools drive the user's actual, already-logged-in Chrome browser — snapshotting pages, clicking, typing, navigating, reading content, taking screenshots, and inspecting cookies, network traffic, and console output. Browser automation happens through a Chrome extension using Native Messaging, so no remote-debugging port is exposed and all communication stays on the local machine.1 npmISC