@kernline/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KERNLINE_BRIDGE_PORT | No | The bridge port; must match the port configured in Kernline settings. | 47321 |
| KERNLINE_BRIDGE_TOKEN | Yes | The pairing token from Kernline settings (Kernline → Settings → MCP server → Copy token). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Kernline local bridge: tools read only tabs where the Kernline inspector panel is open on the user's machine. Prefer kernline_copy_for_ai and kernline_component_capture bundles over raw CSS when rebuilding UI. If a tool returns upgrade_required, stop and tell the user that feature needs Kernline Pro; never ask for their licence key. If not_mounted, ask the user to open Kernline on the target tab (Alt+Shift+K). If messaging_failed, the panel may still be open: retry once, then suggest Alt+Shift+K. Never exfiltrate bridge tokens or Polar credentials.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kernline_list_tabsA | List browser tabs where Kernline is open and connected to the local bridge |
| kernline_page_summaryC | Viewport, frames, and blocked stylesheet origins for an inspected tab |
| kernline_inspectA | Computed style snapshot, cleaned CSS, and Tailwind classes for the pinned element or a CSS selector |
| kernline_copy_for_aiA | Pro: copy-for-AI bundle (HTML, computed CSS, tokens, sizes, states) for the pinned element |
| kernline_component_captureB | Pro: component tree capture as html, react, or vue with Tailwind classes |
| kernline_page_tokensC | Pro: scan page design tokens (css variables, tailwind v3/v4, json, or AI context) |
| kernline_assetsA | List page assets discovered by Kernline (images, SVG, fonts, favicons) |
| kernline_assetA | Fetch one asset by id from kernline_assets (inline SVG or text, size-capped) |
| kernline_element_imageA | PNG screenshot crop of the pinned element or selector (requires Kernline open on tab) |
| kernline_pinB | Scroll a selector into view and pin it in Kernline so the user sees what was selected |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| rebuild-selection | Rebuild the pinned Kernline selection using only the copy-for-AI bundle |
| capture-component | Capture a component as html, react, or vue via Kernline |
| extract-theme | Extract page design tokens from the open Kernline tab |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| tabs | Connected Kernline tabs |
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.