Skip to main content
Glama
ItaiZeilig

jevbridge

by ItaiZeilig
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to jevbridge

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

    • Controlium

      am-will
      A
      license
      Not graded
      quality
      B
      maintenance
      Chrome extension + MCP bridge that gives Claude control over your real browser via CDP, enabling navigation, clicking, typing, scrolling, screenshots, and JS execution with a visible cursor and tab-bring-to-front.
      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.
      20
      1,137 npm
      6
      MIT

    • gotham-browser

      gotham-os
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code to control a real browser using AI for web scraping, competitive intelligence, and UX auditing through the MCP protocol.
      -

    • arc-cdp-mcp

      chmodami
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude Code to control the Arc browser over CDP, including navigation, clicking, form filling, screenshots, and reading console and network traffic.
      11
      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.4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a distinct, non-overlapping purpose: navigate, observe (element table), act (interactions), screenshot, assert (verification), read (text), status, and tabs. No two tools could be confused for the same action; even observe vs read serve clearly different data needs.

    Naming Consistency5/5

    All tools follow a consistent 'browser_' prefix with a lowercase verb: navigate, observe, act, screenshot, assert, read, status, tabs. This uniform verb_noun pattern makes the toolset predictable and easy to reason about.

    Tool Count5/5

    8 tools is well-scoped for a browser automation server, covering navigation, observation, interaction, and verification without unnecessary redundancy. Each tool earns its place in the set.

    Completeness5/5

    The surface covers the full lifecycle of browser automation: navigation, multiple observation modes (element table and plain text), interaction via act, visual capture via screenshot, verification via assert, and infrastructure support via status and tabs. No obvious gaps that would cause agent failures.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources