Site MCP

Your signed-in sites as MCP tools.

Claude gets typed tools for sites that have no API. They run in your own Chrome, with the sign-in you already have.

You:    Is my print still running?
Claude: printeros_printers({ "name": "TEC B-3" })
Site:   { "state": "printing", "percent": 58, "time_left_s": 4560 }

Things to ask

• “What did I last send to Ana, and did she answer?” Outlook
• “What's on this month's phone bill, by line? Attach the PDF.” T-Mobile
• “Find the lecture where we covered backprop and summarize it.” Panopto
• “Is my Duke VM on? Power it on and wait until my app answers.” Duke VCM

Also Canvas, 3DPrinterOS, X and Cloudflare, read with your own sign-in.

How it works

• A Chrome extension calls the site's own endpoints, so Chrome attaches your session cookie itself.
• One call from claude.ai, Claude Desktop or Claude Code, with no clicking through pages.
• If you are signed out, the tool opens the sign-in page. Signing in stays yours.

What it never touches

• No password, token or cookie is read, stored or sent anywhere.
• Nothing is granted at install. Turning a site on asks Chrome for that site only.
• Before a tool changes anything, such as powering off a VM, Chrome asks you to allow it.
• Every adapter is one readable file: see what each site is asked.