Snapstack MCP Server

Local always-on server for SnapStack: browser capture intake + MCP over 127.0.0.1.

Local serverstdioGo

What is the Snapstack MCP server?

Local always-on server for SnapStack: browser capture intake + MCP over 127.0.0.1. That is what the snapstack mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

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.

Getting it running

Installation goes through your MCP client rather than a global install: point it at and on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

The tools it exposes

The server publishes 3 tools. What each one is for:

  • get_screenshots — Lists pending captures as a JSON manifest (stable number, absolute path, dimensions, metadata) — no image bytes, no deletion. Pass numbers (e.g
  • clear_screenshots — Deletes captures. Pass numbers to delete specific ones; omit to clear the whole stack. Numbering restarts at 01 once empty
  • count_screenshots — Number of pending captures, without retrieving them

What it needs from you

  • 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.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Snapstack's toolset — get_screenshots, clear_screenshots, count_screenshots — is a fair guide to whether it matches your workflow. It is maintained by bgaze; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
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.
clear_screenshotsDeletes captures. Pass numbers to delete specific ones; omit to clear the whole stack. Numbering restarts at 01 once empty.
count_screenshotsNumber of pending captures, without retrieving them.

How to install the Snapstack MCP server

{
  "mcpServers": {
    "snapstack-server": {
      "command": "npx",
      "args": ["-y", "and"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • 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.

Example prompts to try

  • Use Snapstack to get screenshots.
  • Use Snapstack to clear screenshots.
  • Use Snapstack to count screenshots.

Frequently asked questions

It connects Snapstack to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (get_screenshots, clear_screenshots, count_screenshots) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Snapstack directly.