Skip to main content
Glama
fredoz0999

pagesnap-mcp

by fredoz0999
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to pagesnap-mcp

No user-submitted related servers found.

    Related Servers

    • Browser MCP Server

      persi123
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to understand web page structure and content through structured data extraction and element discovery using Playwright, eliminating the need for screenshots.
      4
      8 npm
      MIT

    • semantic-dom-mcp

      helmif
      A
      license
      A
      quality
      A
      maintenance
      Drives a real Chromium browser to extract a page's DOM into compact Semantic JSON with Playwright-native locators, enabling AI agents to generate consistent, accurate Playwright tests.
      13
      15 npm
      3
      MIT

    • Playwright MCP

      priyshi
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to interact with web pages through structured accessibility snapshots using Playwright, providing fast and lightweight browser automation without needing vision models.
      8,987,267 npm
      Apache 2.0

    • Playwright MCP

      hyhfish
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides browser automation capabilities for LLMs using Playwright, leveraging structured accessibility snapshots to interact with web pages without needing vision models. It enables tasks like web navigation, data extraction, and automated testing through a lightweight and deterministic toolset.
      7 npm
      Apache 2.0
    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.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool maps to a clearly distinct concern: listing sessions, reading session details, translating locators, and generating prompts. There is no overlap that would cause an agent to select the wrong tool.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: list_sessions, read_session, map_locator, get_prompt. This makes the tool set predictable and easy to navigate.

    Tool Count5/5

    Four tools is a tight, focused scope. Each tool earns its place and supports a distinct step in the PageSnap session inspection workflow without redundancy.

    Completeness4/5

    The read-and-analyze workflow is well covered: list, read, map, and prompt. A minor gap is the lack of session creation or mutation tools, but the descriptions frame this as a read-only inspection tool, so the gaps are acceptable.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources