Skip to main content
Glama
verbalogicproject-creator

preview-bridge

by verbalogicproject-creator
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to preview-bridge

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • Browser MCP Bridge

      robhicks
      A
      license
      Not graded
      quality
      C
      maintenance
      Bridges browser content, developer tools data, and web page interactions with Claude through MCP. Enables page inspection, DOM analysis, JavaScript execution, console monitoring, network activity tracking, and screenshot capture across multiple browser tabs.
      MIT

    • 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

    • Exnos

      golproductions
      A
      license
      Not graded
      quality
      B
      maintenance
      Live browser-state verification for AI coding agents. Provides real-time state of Chrome tabs including URL, title, form fields, buttons, console errors, and visible text via MCP tools.
      224 npm
      -
    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 5 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: session info, event log, runtime errors, page state, and long-polling. The only possible confusion is between get_event_log and get_runtime_errors, since runtime errors may also appear as error-level events in the log, and between get_event_log and tail_events, though the descriptions explicitly frame one as historical and the other as waiting for new events.

    Naming Consistency4/5

    Three tools use the get_ prefix and the remaining two use query_ and tail_, which are understandable action verbs. The names are readable and mostly follow a verb_noun pattern, but the mix of get/query/tail prevents a perfect consistency score.

    Tool Count5/5

    Five tools is well-scoped for a preview bridge debugging surface. Each tool covers a distinct aspect of inspecting live previews without redundancy or bloat.

    Completeness4/5

    The toolset covers the main observability workflow: check connection, read historical events, inspect errors, query live page state, and wait for future events. Minor gaps exist, such as no explicit tool for arbitrary DOM inspection or waiting for the bridge to connect, but the surface is strong for its apparent purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources