Skip to main content
Glama
brnyxx

jev-ra

by brnyxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to jev-ra

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.
      2
      Apache 2.0

    • Claude Chrome MCP

      nonsleepr
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables browser automation through the Claude Chrome Extension, allowing agents to navigate websites, fill forms, take screenshots, and debug web apps via standard MCP protocols.
      1
      MIT

    • browser-mcp-claude

      saGoldberg31
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables remote browser automation via MCP, allowing models to open pages, read snapshots, click, fill, and select elements using Playwright, with built-in security restrictions against sensitive actions.
      -

    • Browserbeam MCP Server

      nyku
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      8 npm
      MIT

    • @domscout/mcp

      jkresearch8
      A
      license
      A
      quality
      C
      maintenance
      Enables browser automation and web data extraction through MCP tools, including Markdown reading, screenshots, structured data extraction, page inspection, and allowlisted site crawling.
      10
      386 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools are clearly distinct, but browser_act overlaps with browser_click/type/select/etc. as a generic 'take a step' action, and browser_run could be confused with act at a higher level. The descriptions help distinguish them, but an agent might occasionally misselect between generic and specific actions.

    Naming Consistency5/5

    All 14 tools follow the exact same browser_<verb> pattern using lowercase snake_case. The naming is highly predictable and consistent, making it easy to infer a tool's purpose from its prefix and verb.

    Tool Count5/5

    14 tools is a well-scoped count for a browser automation server, covering navigation, observation, interaction, and high-level task execution without being bloated. Each tool has a clear role in the workflow.

    Completeness4/5

    The surface covers the core browser lifecycle (open, observe, interact, navigate, close) and includes both low-level and high-level operations. Minor gaps like back/forward navigation or page refresh are missing, but agents can work around them using open or run.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources