Skip to main content
Glama
feder-cr

AIHawk

Official
by feder-cr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to AIHawk

No user-submitted related servers found.

    Related Servers

    • MultiZen

      brahimf3305
      F
      license
      Not graded
      quality
      A
      maintenance
      Exposes 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.
      -

    • MultiZen

      ashleysullivan412
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents and human operators to drive isolated browser profiles with persistent cookies, fingerprints, and proxies through MCP, including navigation, clicking, typing, extraction, screenshots, JavaScript evaluation, tabs, cookies, and waits.
      MIT

    • byob

      daikihunter
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that enables AI coding assistants to drive the real, already-logged-in Chrome browser — navigating pages, clicking, typing, reading content, taking screenshots, and inspecting tabs, cookies, and network traffic through natural language. It works as a Chrome extension, so no remote-debugging port needs to be opened and pages the user is already signed into are fully usable.
      1 npm
      ISC

    • MultiZen

      Petridis03895
      F
      license
      Not graded
      quality
      A
      maintenance
      Exposes a local MCP endpoint that lets AI agents and human operators drive isolated Chromium profiles — each with its own cookies, fingerprint, and proxy — through tools for navigation, clicking, typing, extraction, screenshots, JS evaluation, tabs, and cookie management. Persistent per-profile session state keeps logins and context alive across launches and across AI sessions, so agents can complete real authenticated workflows.
      -

    • CamoFox MCP

      GinevraGirard6229
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects MCP-compatible AI agents to an anti-detection browser server, exposing dozens of tools for navigation, page interaction, search, content extraction, downloads, multi-tab handling, and persistent sessions. It lets agents automate and scrape the web at scale using accessibility snapshots, CSS-selector fallbacks, saved profiles, and batch workflows over stdio or authenticated HTTP transport.
      201 npm
      MIT

    • MultiZen MCP Server

      sita81522
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes a localhost MCP endpoint that lets agents launch and drive isolated, persistent browser profiles — navigating, clicking, typing, extracting, screenshotting, evaluating JS, managing tabs and cookies, and sending raw CDP commands. Each profile keeps its own cookies, login state, fingerprint, and proxy across sessions, enabling real authenticated workflows from Cursor, Claude Desktop, or any MCP client.
      MIT
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    A4.1/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct browser primitive: lifecycle, navigation, reading, interaction, or identity. The read tools separate plain text, HTML structure, snapshot inventory, screenshot, and live watch clearly, and click/type/select/press actions are cleanly differentiated.

    Naming Consistency4/5

    All tools share the browser_ prefix and mostly use an imperative verb, making the family predictable. A few names are noun-like or omit an explicit object (browser_status, browser_snapshot, browser_type), a small deviation from a fully uniform verb_noun pattern.

    Tool Count4/5

    16 tools is slightly above the ideal range, but each tool corresponds to a distinct and useful browser automation primitive. There is no obvious redundant cluster, so the larger count feels purposeful rather than bloated.

    Completeness4/5

    The suite covers the full browsing lifecycle and most common tasks: opening, navigating, reading, clicking, typing, selecting, screenshotting, and watching. Minor gaps include no explicit tab switching or file upload support, but these are edge cases for a typical browser automation workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week

    Resources