
Snapstack Server
Runs as a local daemon on 127.0.0.1:4123 to handle browser screenshots from a companion extension and expose them over MCP. You snap tabs from Chrome or Firefox, the extension POSTs them to the server, and they land as numbered WebP files in ~/.snapstack. Three tools: get_screenshots returns a manifest with paths and metadata (no base64), clear_screenshots deletes by number, and count_screenshots tells you what's waiting. Useful when you want to feed visual context into Claude without copy-pasting URLs or wrestling with vision API limits. The server auto-updates on restart and supports both HTTP and stdio transports, so it works with any MCP client.
- GitHub stars
- 1
- tools
- 3
- transport
- STDIO
- last updated
- Jun 9, 2026
Tools
3 toolsPublic tool metadata for what this MCP can expose to an agent.
get_screenshotsLists pending captures as a JSON manifest (stable number, absolute path, dimensions, metadata) — no image bytes, no deletion. Pass numbers (e.g. [1,3]) to list only those.
Lists pending captures as a JSON manifest (stable number, absolute path, dimensions, metadata) — no image bytes, no deletion. Pass numbers (e.g. [1,3]) to list only those.
No parameter schema in public metadata yet.
clear_screenshotsDeletes captures. Pass numbers to delete specific ones; omit to clear the whole stack. Numbering restarts at 01 once empty.
Deletes captures. Pass numbers to delete specific ones; omit to clear the whole stack. Numbering restarts at 01 once empty.
No parameter schema in public metadata yet.
count_screenshotsNumber of pending captures, without retrieving them.
Number of pending captures, without retrieving them.
No parameter schema in public metadata yet.
Sponsors
Readme
Details
- Repository
- github.com/bgaze/snapstack-server
- Website
- github.com/bgaze/snapstack-extension
- Category
- Web & Browser Automation
- Package
snapstack-server- Transport
- STDIO
- Registry
- MCP registry, active