Skip to main content
Glama
Akarda

mcp-snapshot-filter

by Akarda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-snapshot-filter

No user-submitted related servers found.

    Related Servers

    • chrome-devtools-slim

      mcpslim
      A
      license
      Not graded
      quality
      D
      maintenance
      A token-optimized MCP server that groups Chrome Devtools tools into 8 semantic operations, reducing context window tokens by 69.5% while preserving full functionality.
      2 npm
      1
      MIT

    • cdt-smart-snapshot

      sinnhirl
      A
      license
      A
      quality
      A
      maintenance
      A token-efficient MCP server for Chrome DevTools Protocol that provides smart snapshots, diffing, and screenshot-to-disk tools, reducing token usage dramatically compared to official snapshots.
      8
      9 npm
      Apache 2.0

    • chrome-devtools-mcp-wrapper

      CornWorld
      A
      license
      Not graded
      quality
      C
      maintenance
      Shares one Chrome browser across multiple AI coding sessions via an MCP proxy, adding lifecycle management, tool filtering, and anti-detection while wrapping the upstream chrome-devtools-mcp server.
      10 npm
      2
      MIT
    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

    B3.3/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools target a clear, distinct browser action or data source, such as navigation, input, console messages, network requests, or performance tracing. The main ambiguity is between fill, fill_form, and type_text, though the descriptions reduce the risk of misselection.

    Naming Consistency3/5

    Most names follow a readable snake_case verb_noun pattern like list_pages, navigate_page, and take_snapshot. However, bare verbs such as click, fill, hover, and drag, plus deviations like lighthouse_audit, new_page, and wait_for, break the otherwise consistent style.

    Tool Count2/5

    At 29 tools, the surface is too large for a tightly scoped server and crosses the 25+ threshold. Several specialized debugging capabilities like heap snapshots, Lighthouse audits, and performance tracing could be separated into their own servers or grouped more compactly.

    Completeness4/5

    The tool set covers the full browser workflow well: page lifecycle, navigation, interaction, forms, dialogs, console and network inspection, screenshots, accessibility audits, performance tracing, and memory analysis. Minor gaps like direct cookie/storage manipulation or an explicit scroll helper can be worked around with evaluate_script or emulate.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources