Pilot MCP

Give your AI agent browser superpowers

1 follower

Give your AI agent browser superpowers

1 follower

Your agent inherits your real browser session — already logged into GitHub, Notion, Linear, whatever you use daily. No re-auth. No 2FA. No per-site setup. In-process Playwright (no HTTP layer) = actions in ~5ms instead of ~200ms. 41% faster, 43% smaller context, 13% cheaper than @playwright/mcp in benchmarks. Also: CAPTCHA handoff, iframe support, snapshot diffing, 58 tools with configurable profiles.

Free

Launch tags:Developer Tools•Artificial Intelligence•GitHub

Launch Team

ArticosTest your messaging on your audience, right inside Claude or ChatGPT

Promoted

Maker

📌

Hey PH! 👋 I built pilot because I kept hitting the same wall: my AI agent couldn't log into the sites I actually use. Every session was a fresh headless browser with no identity. The fix turned out to be simple — import cookies directly from your real browser (Chrome, Brave, Arc) via macOS Keychain. Now the agent starts already logged into GitHub, Notion, Linear, whatever you use daily. The in-process architecture was the other big bet: Playwright running in the same process as the MCP server means no HTTP round-trips. Actions take ~5ms instead of ~100–200ms. Happy to answer questions about the architecture, the benchmark methodology, or the cookie import mechanism. What would make this most useful for your workflows?

Report

7mo ago

Pros

Cons

Reviews