Skip to main content
Glama
Sign In
TanasiDesigns

fullpageshot-mcp

by TanasiDesigns
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to fullpageshot-mcp

No user-submitted related servers found.

    Related Servers

    • webshot-mcp

      Brandon-35
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to take screenshots and extract text from web pages using a persistent Chrome browser via CDP, with built-in SSRF protection.
      5 npm
      MIT

    • view-sim-mcp

      itelo
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to open and navigate sites on emulated phones, tablets, and desktops through a connected browser extension, capture transparent PNG screenshots, and render device-emulated screenshots headlessly with Playwright.
      MIT

    • Browser MCP

      sednalabs
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to observe and act on live browser pages through screenshots, bounded actions, responsive captures, console and network inspection, tab operations, and session management over local stdio or authenticated HTTP.
      Apache 2.0
    • Grabbit by BrainGridAI

      Grabbitofficial

      BrainGridAI
      A
      license
      Not graded
      quality
      C
      maintenance
      Screenshot MCP for agents. Send a public URL, get a pixel-perfect CDN image. Full page, header, mobile, or custom. Cookie banner suppression. Handles sites that block headless browsers. Works with Claude, Cursor, Codex. $0.002/grab.
      MIT
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    A3.6/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct action on the controlled browser: open, capture, read file, close, and report status. The only mild overlap is that screenshot can accept a URL directly, which slightly blurs the line with open_url, but otherwise the boundaries are clear.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (open_url, read_screenshot, close_browser) which is consistent and readable. screenshot and browser_status deviate (noun-only), but the set is still predictable.

    Tool Count4/5

    Five tools is a snug, well-scoped set for a headless-browser screenshot server, covering the core lifecycle without bloat. It sits at the lower end but each tool earns its place.

    Completeness4/5

    The browser lifecycle is well covered: open, capture, read back, close, and status. Minor gaps like page interaction (click, scroll, navigate) exist, but for a screenshot-focused purpose the surface is essentially complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources