Snapstack MCP server
io.github.bgaze/snapstack-server·v1.2.3·1 starsLocal always-on server for SnapStack: browser capture intake + MCP over 127.0.0.1.
1 stars45 downloads/wk
Reviews
Write oneNobody has reviewed Snapstack yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Snapstack tools (3, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
clear_screenshotswrite actionDelete pending screenshots from the stack. Pass "numbers" to delete only specific captures
count_screenshotsReturn the number of pending screenshots in the stack without retrieving or clearing them.
get_screenshotsList the pending browser screenshots as a manifest — NO image data. The stack is the local folder
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan13 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 104 days ago8/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Snapstack compares
Against every graded Scraping and browsing MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 58% of 866 Scraping and browsing servers
- Tools
- 3
- the typical Scraping and browsing server has 6
- Tools that change things
- 33%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 1
- more than 50% of 583 Scraping and browsing servers
- Downloads a week
- 45
- more than 29% of 309 Scraping and browsing servers with a package
What its tools let an agent do: 2 read · 1 change
Install Snapstack in Claude Code, Cursor or VS Code
Runs npx -y snapstack-server on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add snapstack-server -- npx -y snapstack-server
What the publisher says
From the Snapstack repository's README, as published. We do not edit it. Read it on GitHub
= 18">
The SnapStack server is a single always-on Node process: it receives browser captures from the extension, stacks them on disk, and serves them to any MCP-capable LLM client over Streamable HTTP. It listens only on 127.0.0.1 — nothing ever leaves your machine.
New here? The full install + usage guide lives in the extension README:
snapstack-extension. This page is the technical reference.
Architecture
One always-on process serves both the extension (capture) and your MCP client, decoupled by a folder on disk.
[MV3 extension] --POST /push (bytes) ┐
▼
[SnapStack server - 127.0.0.1:4123]
├─ writes → stack on disk
└─ MCP /mcp (HTTP) ← MCP clientnamed NN : a stable two-digit number (assigned in capture order, restarts at 01 when the stack empties) plus a timestamp, under ~/.snapstack/.
- Capture — the extension encodes the shot as WebP (PNG fallback), downscales it, and POSTs it here.
- Stack — one image file (.webp/.png) plus a twin .json (url, title, timestamp, dimensions) per capture,
no image bytes); the client reads only the files it needs, by path. Deletion is a separate, explicit clearscreenshots step. Retrieval never deletes.**
- Retrieval — getscreenshots returns a JSON manifest** (number, absolute path, dimensions, metadata —
Requirements
- Node.js ≥ 18 (tested on Node 20). No git needed at runtime.
- An MCP-capable LLM client speaking the HTTP (Streamable HTTP) or stdio transport.
- The snapstack-extension loaded in your browser.
Install & run
On Windows, use an Administrator terminal, otherwise the global npm install and the scheduled-task registration
may get rejected.
The server ships on npm and installation is straightforward on macOS, Linux and Windows:
- Install globally: npm i -g snapstack-server
- Enable background service: snapstack enable
SnapStack auto-starts on login, restarts on crash, and updates itself on each launch. To check its status or if an update is available, simply run snapstack in your terminal.
Available commands:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Snapstack: common questions
- Is Snapstack MCP server safe?
- Mostly: it is graded B (82/100). Read the Snapstack safety report
- How do I install Snapstack?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Snapstack need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Snapstack maintained?
- The last commit was 142 days ago (2026-06-15). The latest release is v1.2.3.
- What can I use instead of Snapstack?
- Servers from other publishers that do the same job: FableCut MCP server, shaft-mcp server and Public Browser MCP server.
- How does Snapstack compare with other Scraping and browsing MCP servers?
- safety score 82/100 (higher than 58% of 866 Scraping and browsing servers); tools 3 (the typical Scraping and browsing server has 6); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Snapstack
Same job from other publishers: the closest match first, then the best rated.
- FableCutZero-dependency browser video editor AI agents drive via a JSON timeline over MCP; ffmpeg export.not reviewedEstablishedA
- shaft-mcpSHAFT browser automation, capture, and offline deterministic failure diagnosisnot reviewedGrowingA
Public BrowserChrome over CDP for AI agents. Blind benchmark vs agent-browser: -33% tokens, -33% cost, -32% timenot reviewedGrowingA- CdpilotZero-dependency browser automation over raw CDP — no Puppeteer, Playwright, or Selenium.not reviewedGrowingB
- Agent BrowserSelf-hosted Chrome for AI agents, with a live noVNC view a human can take over.not reviewedGrowingB