Skip to main content
Glama
DebugBase

Glance

by DebugBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Glance

No user-submitted related servers found.

    Related Servers

    • playwright-mcp

      ademdeniz
      F
      license
      A
      quality
      B
      maintenance
      An MCP server that gives Claude direct control of a real browser via Playwright, enabling AI-driven web testing, autonomous test execution, and live failure analysis through natural language.
      8
      6,888 npm
      3
      -

    • deeporax-browser-mcp

      imfaisii
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server to control a real Chrome browser from Claude, enabling navigation, DOM snapshots, clicks, typing, screenshots, and JS execution via a Chrome extension bridge.
      MIT

    • browser-mcp

      ruggieroromulo
      A
      license
      Not graded
      quality
      C
      maintenance
      Local browser automation MCP server for Claude Code, enabling navigation, clicking, typing, and inspecting real web pages via Google Chrome.
      21 npm
      1
      MIT

    • mare-browser-mcp

      emadklenka
      A
      license
      A
      quality
      C
      maintenance
      A lean, LLM-first browser automation MCP server that gives Claude (or any MCP client) a real Chromium browser to navigate, interact with, and debug web apps.
      14
      6 npm
      6
      MIT

    • Claude Browser

      navarrotech
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that lets Claude control multiple persistent browser tabs inside VS Code, with tools for navigation, clicking, typing, snapshotting pages, and reading console output.
      MIT
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    C2/5.0

    Scored across 32 tools

    Disambiguation4/5

    Tool names are mostly distinct, with browser_* and test_* prefixes clearly separating categories. However, some potential overlap exists between browser_screenshot and browser_snapshot, and test_fill_form could be confused with browser_type. Overall, the names are specific enough for an agent to differentiate.

    Naming Consistency5/5

    All tools follow a consistent pattern of prefix_object_action (e.g., browser_navigate, test_scenario_run, session_start). This uniformity makes the set predictable and easy to navigate.

    Tool Count4/5

    With 32 tools, the count is high but appropriate for a comprehensive browser automation and testing server. Each tool seems justified given the domain (browser control, testing, sessions, visual checks), though a slight reduction could improve simplicity.

    Completeness4/5

    The tool surface covers major browser interactions, testing scenarios, session management, and visual comparisons. Missing elements like network mocking or cookie management are notable, but core workflows appear well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources