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.
      40
      1,043 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.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct concern: listing tabs, checking connection/target state, navigating, reading the page, acting on the page, and asserting outcomes. The descriptions clearly separate browser_status from browser_tabs by emphasizing connection state versus the full tab list.

    Naming Consistency4/5

    All tools share a consistent browser_ prefix and lowercase style, which makes the set predictable. However, the second part mixes nouns (tabs, status) with verbs (navigate, observe, act, assert), so the pattern is not perfectly uniform.

    Tool Count5/5

    Six tools is a well-scoped size for browser automation. Each tool covers a necessary phase of the workflow without redundancy or bloat.

    Completeness4/5

    The core browser automation lifecycle is covered: list tabs, target, navigate, observe, act, and assert. Minor gaps exist around tab lifecycle operations like creating or closing tabs, but these don't prevent typical automation workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources