@kernline/mcp
Related Servers
Alternatives to @kernline/mcp
No user-submitted related servers found.
Related 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-
- AlicenseNot gradedqualityAmaintenanceExposes a governed, OAuth-gated MCP endpoint that lets web AI clients such as Claude, ChatGPT, Grok, and Postman work directly on your local machine. It enables file reading and editing, whitelisted shell commands, search, Git and SQLite access, browser and DevTools automation, background tasks, localhost fetches, clipboard, notifications, and port management.MIT
- 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.-
- AlicenseNot gradedqualityAmaintenanceConnects web-based AI chat clients such as Claude, ChatGPT, Grok, and Postman to a local machine through a single OAuth-gated MCP endpoint, so they can build and edit projects, run whitelisted shell commands, search files, inspect databases and local APIs, drive browsers and DevTools, manage background jobs, and control Postman without granting unrestricted shell access. It also supports local IDEs and offline use by connecting directly over localhost.MIT
- 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
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.