Skip to main content
Glama
AMARA-Khaled

wrave-mcp

by AMARA-Khaled
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to wrave-mcp

No user-submitted related servers found.

    Related Servers

    • jev-browser

      tontoko
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables browser automation through MCP with native Playwright operations, deterministic assertions, and natural-language grounded actions, structured extraction, and bounded agent workflows over live page elements.
      13
      Apache 2.0

    • jev-ra

      brnyxx
      A
      license
      A
      quality
      A
      maintenance
      Enables browser automation for coding agents via MCP, allowing them to open pages, search, extract data, click, type, and complete multi-step tasks with fast single-round-trip decisions.
      14
      19 PyPI
      4
      MIT

    • agent-in-browser

      Gwakko
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents and MCP clients to drive real Chrome, Edge, Brave, and Firefox browsers through native automation protocols. It exposes tools for navigation, page snapshots, form filling, clicks, screenshots, console/network inspection, and tab management.
      23
      MIT
    • hronaut by hronaut

      hronautofficial

      hronaut
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to control a persistent local browser with live tabs, navigation, interaction, inspection, and state management through MCP.
      6
      -
    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

    A3.5/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (tab management, content extraction, interaction, utilities). Some overlap exists between get_dom_tree, get_accessibility_tree, and get_snapshot, and compound tools like click_and_read combine actions but descriptions clarify their use.

    Naming Consistency5/5

    All tools follow the consistent pattern 'wrave_' + verb + noun (e.g., list_tabs, close_tab, take_screenshot, execute_script). The naming is uniform and predictable, with no style mixing.

    Tool Count4/5

    At 21 tools, the server is on the heavy side, but the scope (browser automation) justifies the breadth. It covers tab management, page inspection, interaction, and auxiliary functions without being excessive.

    Completeness4/5

    Core browser automation workflows are well covered: tabs (open, close, focus, reload), content extraction (DOM, AX, screenshot, snapshot), interaction (click, type, keys, scroll), and utilities (cookies, PDF, console). Minor gaps like hover, back/forward navigation, or wait-for-element are absent but not critical.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources