Skip to main content
Glama
SAITS-Swiss-AI-Tech-Services

jev-mcp

by SAITS-Swiss-AI-Tech-Services
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to jev-mcp

No user-submitted related servers found.

    Related Servers

    • chromeboost

      lordamdal
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets Claude Code drive your own Chrome browser with human-like clicks, drags, and typing. It uses your real sessions and logins, and pauses for your confirmation on anything irreversible.
      8
      MIT

    • jevbridge

      ItaiZeilig
      A
      license
      A
      quality
      A
      maintenance
      Enables Claude Code to control your actual logged-in Chrome browser through an MV3 extension, perceiving pages as element tables and performing actions such as navigation, clicks, typing, and assertions via CDP.
      6
      MIT

    • ultrabrowse

      narekgevorgyan
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to delegate complex web browsing goals to a real Chrome instance driven by Jev, completing tasks end-to-end in ~300ms per decision and returning only the final result.
      11
      1
      MIT

    • chrome-mcp

      Mehmoodqureshi
      A
      license
      B
      quality
      A
      maintenance
      Enables controlling a real Chrome browser from MCP hosts like Claude, with extension-based or CDP fallback, supporting tabs, navigation, interaction, and page reading tools.
      40
      1,043 npm
      6
      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

    A4.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools are sharply delineated: browser_task performs autonomous multi-step interaction, browser_read is a read-only page fetch, and browser_status is a diagnostic readiness check. Both browser tools explicitly cross-reference when the other should be used, removing any ambiguity.

    Naming Consistency4/5

    All tools share the browser_ prefix, making the family instantly recognizable. However, browser_read uses a verb while browser_task and browser_status use nouns, so the pattern is not perfectly uniform.

    Tool Count5/5

    Three tools is a well-scoped set for the server's purpose: one for autonomous interaction, one for passive reading, and one for environment status. No tool feels redundant or extraneous.

    Completeness5/5

    The tool surface covers the full lifecycle of a browser automation session: verify readiness, read a single page, and execute multi-step tasks. Limitations are documented rather than missing functionality, and no obvious dead ends remain for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources