Skip to main content
Glama
minseokchoi87

Vibeside MCP

by minseokchoi87
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Vibeside MCP

No user-submitted related servers found.

    Related Servers

    • Chrome DevTools MCP

      Anirbandz
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding assistants to control and inspect a live Chrome browser for automation, debugging, performance analysis, network monitoring, and DOM interaction through Chrome DevTools Protocol.
      2,848,483 npm
      Apache 2.0

    • Chrome DevTools MCP

      dinesh-nalla-se
      A
      license
      Not graded
      quality
      D
      maintenance
      Lets AI coding assistants control and inspect a live Chrome browser using full Chrome DevTools capabilities for browser automation, debugging, and performance analysis.
      2,848,483 npm
      Apache 2.0

    • chrome-devtools-mcp

      zhang77-X
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding assistants to control and inspect a live Chrome browser through Chrome DevTools for automation, debugging, and performance analysis.
      2,848,483 npm
      Apache 2.0

    • Chrome DevTools MCP

      khawjaahmad
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI coding assistants to control and inspect a live Chrome browser for automated debugging, performance analysis, and web interaction. It leverages Puppeteer and Chrome DevTools to provide capabilities like network monitoring, console logging, and automated browser actions.
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    C2.9/5.0

    Scored across 70 tools

    Disambiguation3/5

    Most tools target distinct resources/actions, but there are clear overlaps: vibeside_compare_visual_diff is an explicit alias for vibeside_visual_diff, vibeside_capture_viewport_matrix overlaps with vibeside_screenshot, and vibeside_inspect_contrast overlaps with vibeside_audit_accessibility. With 70 tools, an agent can usually pick correctly, but these collisions create real misselection risk.

    Naming Consistency3/5

    All tools share the vibeside_ prefix and snake_case, which helps, but verb placement is inconsistent: verb_noun (inspect_contrast, list_tabs) versus noun_verb (telemetry_get, hmr_clear, cluster_status, media_events). The mixed ordering makes the set less predictable than a single convention would be.

    Tool Count1/5

    70 tools is far beyond what this domain warrants; the calibration explicitly treats 50+ tools as an extreme mismatch. Many adjacent tools (e.g., multiple telemetry clears, multiple status tools) could be consolidated without losing capability.

    Completeness4/5

    The surface is broad and lifecycle-complete: browser lifecycle, profiles, tabs, DOM/CSS/accessibility inspection, telemetry, HMR, storage, mocks, emulation, throttling, clusters, and media. Minor gaps like keyboard key events, scrolling, or explicit wait/assert operations exist, but core workflows are well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources