Loading...
Loading...
Found 2 Skills
Drive a remote chrome-devtools-mcp server (typically on a tailnet) over HTTPS using the chrome-devtools CLI. Use this when the user wants to navigate, screenshot, inspect, or evaluate JavaScript on a browser running on another host (e.g. a Tailscale-connected Mac mini or a CI runner) — and you don't have a local Chrome to control. Examples of triggers ("open <url> on the lab mac", "take a screenshot of the browser on host X", "evaluate this on the remote browser").
Drive the real Chrome on Iliyas's Windows PC over CDP — the same browser he uses himself, signed in to his accounts (Vercel, Google Cloud, Heroku, and others). Use it to fetch data that sits behind his logins, open and debug a page live, watch a flow together, intercept requests, or set the browser's proxy / exit country. Use it only when Iliyas explicitly asks for his real / host / Windows browser — everything it does is visible on his screen.