Skip to main content
Glama
bgaze

SnapStack Server

by bgaze
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to SnapStack Server

  • MCP Screenshot Server

    sethbang
    A
    license
    A
    quality
    A
    maintenance
    Enables capturing screenshots of web pages and local HTML files through a simple MCP tool interface using Puppeteer with configurable options for dimensions and output paths.
    2
    464 npm
    30
    Apache 2.0

Related Servers

  • image-vision-mcp

    moton16
    A
    license
    Not graded
    quality
    C
    maintenance
    Zero-dependency MCP server that enables text-only models to "see" images via a read_image tool, which forwards the image (local path, URL, data URL, or base64) to any OpenAI-compatible vision API and returns the textual description to the main model.
    53 npm
    1
    MIT

  • MCP-URL2SNAP

    Abhi5h3k
    F
    license
    A
    quality
    D
    maintenance
    A lightweight Model Context Protocol (MCP) server that enables your LLM to capture screenshots of any specified URL and return only the access URL for the captured image. This tool simplifies the process of generating and sharing webpage snapshots, making it perfect for integrating visual capture ca
    1
    2
    -

  • SnapAPI MCP Server

    Sleywill
    A
    license
    A
    quality
    D
    maintenance
    MCP server for the SnapAPI web capture API. Take screenshots, scrape pages, extract structured data, generate PDFs, record videos, and run AI analysis on any URL — all from Claude, Cursor, VS Code, or any MCP client. 9 tools, 30+ device presets, ad/cookie blocking. Install: npx snapapi-mcp
    9
    7 npm
    MIT

  • Screen MCP

    jeandelest
    F
    license
    A
    quality
    C
    maintenance
    Enables LLMs to capture screenshots and screen recordings through MCP with chunked session-based transfers for reliable image consumption. Supports multi-monitor selection, timeline capture, and compatibility with both vision and non-vision language models.
    11
    1
    -
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.7/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct purpose: clearing, counting, and listing screenshots. There is no overlap in functionality, and the descriptions clearly differentiate them.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (clear_screenshots, count_screenshots, get_screenshots), making them predictable and easy to understand.

Tool Count5/5

Three tools are appropriate for the narrow domain of managing a screenshot stack. Each tool provides essential functionality without redundancy or unnecessary complexity.

Completeness5/5

The tool set covers the core operations needed to manage pending screenshots: listing metadata, counting, and clearing. Since capture is handled externally by a browser extension, the server's surface is complete.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources