bgaze/snapstack-server

Overview

Local always-on server for SnapStack. Receives browser captures and serves them to any MCP-capable LLM client over MCP (Streamable HTTP + stdio). Listens on 127.0.0.1 only.

Best for

Best for
Developers needing a local MCP bridge between SnapStack and LLM clients

Use cases

• Integrating browser captures into LLM workflows
• Providing a local MCP endpoint for SnapStack data
• Enabling MCP-based LLM clients to access browser snapshots

Notes

Local always-on server for SnapStack. Receives browser captures and serves them to any MCP-capable LLM client over MCP (Streamable HTTP + stdio). Listens on 127.0.0.1 only.

0 stars on GitHub. Last updated 2026-06-15. Licensed MIT.

Use cases

• Integrating browser captures into LLM workflows
• Providing a local MCP endpoint for SnapStack data
• Enabling MCP-based LLM clients to access browser snapshots

Pros

• Simple local setup
• Supports both Streamable HTTP and stdio MCP transports
• Always-on server ensures captures are available on demand

Cons

• Only listens on localhost (127.0.0.1) limiting remote access
• Requires SnapStack to be running separately
• Zero stars indicates limited community adoption

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.