Skip to main content
Glama
samsebeingener

VisBug MCP Bridge

by samsebeingener
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to VisBug MCP Bridge

No user-submitted related servers found.

    Related Servers

    • visbug-mcp

      mambari
      F
      license
      A
      quality
      D
      maintenance
      Captures visual changes made with VisBug in the browser and exposes them to Claude Code via MCP, allowing developers to apply design modifications to source files directly from natural language.
      3
      2
      -

    • tell-ai-ui-critic

      ashishpatill
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that captures rendered UI, diagnoses design tells and consistency drift, and generates redesign diffs from natural language art direction, all within Cursor.
      2
      1
      MIT

    • pholly-figma-mcp

      mubzie
      A
      license
      Not graded
      quality
      B
      maintenance
      Local-first MCP bridge for live Figma documents, enabling design inspection, editing, asset export, component authoring, and variable management through a plugin and WebSocket server without consuming Figma REST API requests.
      1
      MIT

    • MC Figma Bridge

      mochammad123
      F
      license
      B
      quality
      D
      maintenance
      Enables Cursor (MCP client) to interact with an active Figma document through a local WebSocket bridge and Figma plugin, providing tools to read and modify canvas elements like text and frames.
      6
      -

    • Perfect

      Gtarafdar
      A
      license
      Not graded
      quality
      A
      maintenance
      Unofficial open-source MCP bridge that gives Cursor agents hands in your real Chrome browser. Enables navigation, clicking, filling, screenshots, and other browser actions with permission modes.
      8
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_changes retrieves captured changes, apply_changes marks them as applied, and clear_changes empties the buffer. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with underscores: get_changes, apply_changes, clear_changes. The verbs are imperative and the noun is uniform, providing a predictable and clear naming scheme.

    Tool Count5/5

    With only 3 tools, the set is perfectly scoped for managing a single buffer of visual changes. Each tool serves a necessary and distinct function, and no tool feels extraneous or missing for this focused purpose.

    Completeness4/5

    The tool set covers the core operations for managing the changes buffer: reading, marking as applied, and clearing. While there is no tool to revert individual changes or directly apply them to files, those functions are intentionally handled externally, making the set complete for its defined scope.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources