Snap_sense

Created By
Abhi5h3ka year ago
Overview

What is Snap_sense?

Snap_sense is a lightweight Model Context Protocol (MCP) server that allows AI models to capture screenshots of specified URLs and return the access URL for the captured images. This tool is designed to simplify the process of generating and sharing webpage snapshots, making it ideal for integration into AI applications and automation workflows.

How to use Snap_sense?

To use Snap_sense, clone the repository, set up the required environment, and run the server. You can then register the server with compatible AI applications like Claude Desktop to start capturing screenshots.

Key features of Snap_sense?

  • Real-time email verification
  • Seamless integration with MCP-compatible LLMs
  • Easy setup using Python and the MCP SDK

Use cases of Snap_sense?

  1. Capturing webpage snapshots for documentation
  2. Integrating visual capture capabilities into AI applications
  3. Automating the process of generating and sharing screenshots

FAQ from Snap_sense?

  • What is the Model Context Protocol (MCP)?

MCP is a standardized protocol that streamlines communication between AI models and external systems.

  • What are the requirements to run Snap_sense?

You need Python 3.11.0 or higher and the UV package.

  • Is Snap_sense free to use?

Yes! Snap_sense is open-source and free to use.

Server Config

{
  "mcpServers": {
    "snap_sense": {
      "command": "uv",
      "args": [
        "--directory",
        "/ABSOLUTE/PATH/TO/PARENT/FOLDER/weather",
        "run",
        "server.py"
      ],
      "env": {
        "ABSTRACT_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Abhi5h3k
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago