We've compared 2 tools across pricing, features, ratings, and reviews to help you make an informed decision. No paid placements — just facts.
Compare different tools →| Feature | AIHawk Developer Tools | MetaMCP Developer Tools |
|---|---|---|
| Rating | No reviews yet | No reviews yet |
| Pricing | Free as of Sep 30, 2026 | — |
| Pricing Model | Free | Free |
| Free Plan | ||
| Free Trial | ||
| API Available | ||
| Verified | ||
| Founded | — | — |
| HQ | — | — |
| Team Size | 2-10 | — |
| Platforms | — | — |
| Top Integrations | — | Claude DesktopCursorClineWindsurf+4 more |
| Key Features |
|
|
| Description | AIHawk (now published under the name invisible_playwright_mcp, with AIHawk kept as its established brand) is an open-source anti-detect browser and web-browsing agent built on Playwright, distributed as an MCP server so coding assistants like Claude Code, Codex, and Gemini CLI can browse the web without triggering captchas or anti-bot blocks. It ships two ways to use it: as an MCP server plugged into an existing coding assistant, or as a standalone web UI (a chat panel next to a live browser view) that works with any OpenRouter model and key. The engine drives a stealth Firefox build with configurable proxy, browser-fingerprint seed, and persistent profile support, so logins and cookies survive across restarts. Everything runs locally with no server of AIHawk's own: the sites visited see the browser as any normal Firefox would, and only the assistant's own model provider sees the conversation. The project has 31,700+ GitHub stars and 4,700+ forks, and its author previously built the well-known LinkedIn auto-apply tool under the same AIHawk name. | MetaMCP is self-hostable middleware that aggregates and proxies multiple Model Context Protocol (MCP) servers behind a single endpoint, managed through a GUI app with a one-click app store and multi-workspace isolation. Because it acts as an MCP server itself, it works with any MCP client (Claude Desktop, Cursor, Cline, Windsurf) and lets developers switch server sets per project and toggle individual tools. It's aimed at developers and teams running many MCP integrations who want centralized, private control rather than configuring each server separately in every client. |