tactab
Related Servers
Alternatives to tactab
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol server for Chrome tab automation using the Chrome DevTools Protocol, enabling AI agents to select tabs, capture screenshots, and interact with web pages via CSS viewport coordinates.9MIT
- AlicenseAqualityAmaintenanceOpen-source Chrome extension + MCP server that lets AI agents drive your real, signed-in Chrome by reading the live DOM (no screenshots).72205MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server and Chrome extension that allows users to select browser DOM elements via a keyboard shortcut to provide detailed technical context to AI coding tools. It captures HTML attributes, CSS styles, and React component metadata, enabling agents to analyze and modify web elements directly.599MIT
- AlicenseBqualityAmaintenanceA lightweight 30KB MCP browser automation server that uses raw Chrome DevTools Protocol to enable AI agents to browse the web, take screenshots, interact with elements, and capture live page events like console logs and network requests.2651 npm19MIT
- AlicenseNot gradedqualityDmaintenanceAn extension-based MCP server that enables AI assistants to control your browser, leveraging existing sessions and login states for automation and content analysis. It provides over 20 tools for semantic tab search, interactive element manipulation, and network monitoring directly within your daily Chrome environment.MIT
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding tools drive the user's own already-logged-in Chrome through a companion extension, using snapshots and refs to click, type, navigate, read, screenshot, and inspect pages. It enables automation of authenticated sites, tab and network management, and form filling without headless browsers or remote-debugging ports, keeping all communication on the local machine.1 npmISC
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of selecting the wrong tool. Its purpose is clearly stated as executing browser actions via a Chrome extension bridge.
The single tool follows a clear verb_noun snake_case pattern (automate_website). There are no mixed conventions or naming conflicts to penalize.
A single tool is borderline thin for a browser automation server. It could be intentional as a generic executor, but the set lacks distinct operations that agents would typically expect.
The surface provides one generic action executor with no explicit operations, parameters, or lifecycle coverage. Agents lack discoverable building blocks for common browser automation tasks, creating likely gaps.