AIHawk
OfficialRelated Servers
Alternatives to AIHawk
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables real browser automation as tools in Cursor, Claude Desktop, Windsurf, and any MCP-compatible client, allowing AI agents to interact with web pages through natural language.8MIT
- AlicenseAqualityBmaintenanceMCP server that gives AI coding assistants direct access to the browser — navigate, click, fill forms, run JavaScript, take screenshots, and read page content.11161MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and clients to control a real Chromium browser through MCP tool calls, including navigation, clicking, typing, JavaScript evaluation, screenshots, and DOM snapshots. Supports multiple isolated sessions over authenticated HTTP with no disk writes.Apache 2.0
- AlicenseAqualityAmaintenanceMCP server that lets AI agents drive your real Chromium browser with your existing signed-in sessions, providing visible, local, and inspectable automation for tasks like navigation, clicking, typing, and form filling.251Apache 2.0
- FlicenseNot gradedqualityBmaintenanceAn MCP server that lets AI assistants drive real Chromium browsers — navigate, click, type, read pages, run OCR, and record network traffic. 43 tools, credentials stay local, zero telemetry.-
- FlicenseNot gradedqualityBmaintenanceEnables Claude Code to control a real browser using AI for web scraping, competitive intelligence, and UX auditing through the MCP protocol.-
TDQS
Scored across 16 tools
Most tools have clearly distinct purposes (click vs click_at, type vs press_key, select_option vs evaluate), and descriptions actively steer callers between near-neighbors. The reading trio (read_text/read_html/snapshot) and the pair (browser_list vs browser_status) overlap somewhat, but the descriptions draw sharp boundaries and recommend when to use each.
Every tool uses the identical browser_ prefix followed by a clear verb or verb_noun (open, close, navigate, click, click_at, type, press_key, select_option). No convention mixing; names are fully predictable.
16 tools is slightly heavy but each maps to a genuine, non-redundant browser capability spanning lifecycle, navigation, reading, and interaction. Nothing feels padded, though a few read tools could plausibly be merged.
The surface covers lifecycle (open/close/list/status), navigation, multiple read modes, and the key interaction primitives (click, click_at, type, select_option, press_key, evaluate). Minor gaps exist: no tab/page switching despite multi-page support, and no file upload, waiting, or back/forward/refresh helpers.