Tag

#privacy

52 results found

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)

10 days ago
Logly
@logly-uk

Logly MCP server Query your Logly web analytics from Claude, Cursor, or any Model Context Protocol client. Logly is privacy-first web analytics — under 1 KB, cookie-free, GDPR compliant by design. This server exposes your analytics over MCP so an AI assistant can answer questions like "how did traffic change this week?" or "where is my signup funnel losing people?" — and even hand you the install snippet for a new site. Requirements Node.js 18 or newer A Logly account and an API key — create one in Settings → API keys in your Logly dashboard. The key looks like logly_a1b2c3... and is shown only once. Setup The server runs via npx — no install step needed. Claude Desktop Edit claude_desktop_config.json (Settings → Developer → Edit Config): { "mcpServers": { "logly": { "command": "npx", "args": ["-y", "@logly-uk/mcp"], "env": { "LOGLY_API_KEY": "logly_your_key_here" } } } } Restart Claude Desktop. Claude Code claude mcp add logly -e LOGLY_API_KEY=logly_your_key_here -- npx -y @logly-uk/mcp Cursor Add to .cursor/mcp.json in your project (or the global one): { "mcpServers": { "logly": { "command": "npx", "args": ["-y", "@logly-uk/mcp"], "env": { "LOGLY_API_KEY": "logly_your_key_here" } } } } Tools Tool What it does logly_list_sites List every site in your account with its site ID — start here. logly_stats Pageviews, sessions, visitors, bounce rate, avg duration, daily series, previous-period comparison. logly_breakdown Top pages, referrers, countries and device/browser split. logly_realtime Visitors active right now. logly_events Custom event counts. logly_funnels List a site's conversion funnels and their steps. logly_funnel_results Completion counts and drop-off per funnel step. logly_install_snippet The <script> tag to add Logly to a site's <head>. Date filters Stats tools accept a days window (7, 30 or 90 — defaults to 30) or an explicit from / to pair (YYYY-MM-DD). If both are given, from/to wins. Environment variables Variable Required Purpose LOGLY_API_KEY yes Your Logly API key. LOGLY_API_BASE no Override the API base URL (default https://app.logly.uk).

17 hours ago