Browser control + session recording MCP for AI coding agents (Claude Code, Cursor) — real Chrome.
Thinkrun MCP server exists for a simple reason — assistants are far more useful when they can act on Thinkrun directly instead of describing what you should do. Browser control + session recording MCP for AI coding agents (Claude Code, Cursor) — real Chrome.
Stop screenshotting bugs and typing paragraphs to explain them. ThinkRun records any browser session — or lets your agent record what it built — and turns it into structured context your AI coding agent can act on: every click, the console, network requests, your voice narration, and screenshots, all time-synced. Not just a screenshot. Not just a video.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once Thinkrun is connected, these are the calls the assistant has available:
Cursor — .cursor/mcp.jsonCline — VS Code settings → Cline MCP Serversweb-browse — browse the web programmatically: drive a real or cloud browser to navigate, interact, extract, and screenshotux-audit — walk through a product UI as a real user, screenshot every step, and produce a structured UX report with a prioritized fix listthinkbrowse-cli — drive the browser from shell scripts via the thinkrun CLIthinkbrowse-mcp — drive the browser through the ThinkRun MCP server's toolsAmong the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Thinkrun's toolset — Cursor, Cline, web-browse and 3 more — is a fair guide to whether it matches your workflow. It is maintained by dundas; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Cursor | .cursor/mcp.json |
| Cline | VS Code settings → Cline MCP Servers |
| web-browse | browse the web programmatically: drive a real or cloud browser to navigate, interact, extract, and screenshot. |
| ux-audit | walk through a product UI as a real user, screenshot every step, and produce a structured UX report with a prioritized fix list. |
| thinkbrowse-cli | drive the browser from shell scripts via the thinkrun CLI. |
| thinkbrowse-mcp | drive the browser through the ThinkRun MCP server's tools. |
{
"mcpServers": {
"thinkrun": {
"command": "npx",
"args": ["@thinkrun/mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
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.