Site Sense

What is Site Sense?

Site Sense gives AI coding assistants read-only access to a user's current browser tab via a browser extension and the Model Context Protocol. It captures the accessibility tree and screenshot of the active page, enabling the AI to see web portals without cloud storage, network uploads, or manual screen‑sharing.

How to use Site Sense?

Clone the repository, install dependencies, build the extension, and load it unpacked in Chrome or Edge. Add the MCP server configuration to your CLI’s MCP config file. The first time the tool is called, a popup appears to grant permission; subsequent captures are automatic until the terminal session ends. Invoke the AI with queries like “What’s on my browser tab?”.

Key features of Site Sense

• Two MCP tools: site_sense_capture and site_sense_status
• Per‑page default permission mode; all‑sites mode available via toggle
• No network traffic (Unix socket + native messaging)
• No persistent storage – memory only, gone on disconnect
• Session‑scoped permissions that reset when CLI disconnects
• Skips form values and strips URL tokens for privacy

Use cases of Site Sense

• AI assistant checking NSG rules in Azure Portal without manual screenshots
• AI reading dashboard metrics or error messages during troubleshooting
• AI examining configuration pages in SaaS applications
• AI verifying UI state changes during development workflows

FAQ from Site Sense

What MCP tools does Site Sense provide?

Two tools: site_sense_capture (returns accessibility tree + screenshot of active tab) and site_sense_status (checks connection and session approval).

How does Site Sense keep the data secure?

Data never leaves the machine – native messaging runs over a Unix domain socket, not the network. Nothing is stored persistently; all data is discarded when the CLI disconnects. Site Sense is read‑only (never clicks or types) and hides form values and URL tokens.

Which browsers and runtimes are supported?

Chrome and Edge are supported via native messaging. The MCP server requires Node.js. The extension is built with TypeScript + Vite.

What dependencies does Site Sense require?

Node.js, npm, and a recent version of Chrome or Edge with Developer mode enabled. The extension bundle is 9 KB and has only 7 total dependencies.

How do I troubleshoot a failed capture?

Ensure the extension is loaded (edge://extensions or chrome://extensions), you are on an http:// or https:// page, and the extension icon is not grayed out. If the content script isn’t responding, click the extension icon on the page or enable all‑sites mode.