tether
Related Servers
Alternatives to tether
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server + Chrome extension that gives AI coding agents control of your real browser with existing sessions, logins, and cookies. Works with Cursor, Claude, Windsurf.24154 npm59MIT
- AlicenseNot gradedqualityBmaintenanceChrome extension + MCP server. Lets coding agents (Claude Code, Codex CLI) drive your real Chrome — sessions intact, 2FA stays with the user. 26 browser tools: form fill on React/CodeMirror/Monaco, privileged fetch that bypasses page CSP, authenticated downloads, in-extension docx parsing. Battle-tested by 400+ hours of real agentic browser work before public v0.9 release.3MIT
- AlicenseNot gradedqualityBmaintenanceA local MCP server that lets Claude Code and Codex drive your real, already-logged-in Chrome — reading pages, clicking, typing, filling forms, navigating, managing tabs and taking screenshots — without Playwright. It pairs with a companion extension over a local WebSocket, with an on/off switch and a domain blocklist so the AI acts only where you allow.MIT
- AlicenseNot gradedqualityDmaintenanceChrome extension + MCP bridge that gives Claude control over your real browser via CDP, enabling navigation, clicking, typing, scrolling, screenshots, and JS execution with a visible cursor and tab-bring-to-front.1MIT
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding tools drive the user's own already-logged-in Chrome — clicking, typing, reading pages, taking screenshots, and inspecting cookies, network, and console through the extension rather than a debug port. All communication stays on the machine, with agent-opened tabs grouped and kept out of focus.1 npmISC
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding assistants drive the user's own already-signed-in Chrome, so agents can read logged-in pages, click, fill forms, navigate, screenshot, inspect network traffic and storage, and run multi-step browser workflows without a separate headless browser or remote debugging port. All communication stays on the user's machine and agent-opened tabs are grouped so they never steal focus.1 npmISC
TDQS
Scored across 53 tools
Most tools target a clear browser resource or action, and the descriptions give strong boundaries between page reading (snapshot, read_text, screenshot, run_js) and interaction. A few boundaries are softer: network_requests vs. network_request, site_list vs. site_map vs. site_sessions, and save_script vs. install_userscript can require reading descriptions carefully.
Names are consistently lowercase snake_case and mostly follow recognizable verb_noun or category-prefix patterns. There are minor deviations such as bare verbs (click, type, navigate), noun-first site_list/site_sessions, and noun-only network_requests/cookies, but the conventions remain readable and predictable.
The server covers a very broad browser-automation surface, but 53 tools is far beyond a well-scoped set and imposes a significant selection burden. Many tools earn their place functionally, yet the total count is too high for one coherent toolset.
The surface is unusually complete for browser automation: tabs, interaction, page reading, network/console inspection, sessions, styles, scripts, watchers, media, downloads, and site memory are all covered. Minor gaps remain, such as setting/deleting cookies and explicit dialog handling, though run_js can work around many of them.