Fast browser automation MCP server for LLMs — persistent Chromium, ref-based interaction, cookie migration
Fast browser automation MCP server for LLMs — persistent Chromium, ref-based interaction, cookie migration. That is what the pilot mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Native mode avoids chrome.tabs.captureVisibleTab() entirely, so screenshots do not depend on Chrome being foregrounded, a tab being visibly active, or the extension service worker being fresh.
pilot-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The server publishes 4 tools. What each one is for:
Profile — Toolscore — 9standard — 40full — 69Configuration is passed through the environment: PILOT_PROFILE. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Pilot's toolset — Profile, core, standard and 1 more — is a fair guide to whether it matches your workflow. It is maintained by tacosyhorchata; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Profile | Tools |
| core | 9 |
| standard | 40 |
| full | 69 |
{
"mcpServers": {
"pilot": {
"command": "npx",
"args": ["-y", "pilot-mcp"],
"env": { "PILOT_PROFILE": "standard" }
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PILOT_PROFILE | Configuration value read at startup. | Optional |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.