YotamNordman/site-sense
Give your AI coding CLI eyes into web portals. No cloud. No storage. Read-only.
Platform-specific configuration:
{
"mcpServers": {
"site-sense": {
"command": "npx",
"args": [
"-y",
"site-sense"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
[](https://github.com/YotamNordman/site-sense/actions/workflows/ci.yml) [](LICENSE)
Give your AI coding CLI eyes into web portals. No cloud. No storage. Read-only.
<p align="center"> </p>
You're in a conversation with your AI assistant. It says *"go to the Azure Portal and check the NSG rules."* You alt-tab, navigate, screenshot, describe what you see, paste it back. You are the human middleware.
site-sense eliminates this. The AI calls an MCP tool → your browser extension captures the active tab → the AI sees what you see.
git clone https://github.com/YotamNordman/site-sense.git
cd site-sense
npm install && npm run build
npm run setup -- --browser edge # or chromeLoad the extension in your browser:
edge://extensions (or chrome://extensions)dist/extension/Add to your CLI's MCP config:
{
"mcpServers": {
"site-sense": {
"command": "node",
"args": ["/path/to/site-sense/dist/bridge/src/index.js"]
}
}
}Then ask your AI: "What's on my browser tab?"
First time → popup appears → click Allow → done. All subsequent captures are automatic until you close the terminal.
CLI (Claude Code / Copilot CLI)
↕ stdin/stdout (MCP protocol)
MCP Server (TypeScript)
↕ Unix domain socket (no network)
Native Host (thin relay)
↕ Chrome native messaging (stdio)
Extension (TypeScript, Manifest V3)
↕ inject → content → background
Browser Tab → accessibility tree + screenshotTwo MCP tools:
| Tool | What it does | |---|---| | site_sense_capture | Accessibility tree + screenshot of active tab | | site_sense_status | Check connection and session
Loading reviews...