Pure-Go browser for AI: fetch pages, render JS without Chromium, return clean Markdown over MCP.
Unblink MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Pure-Go browser for AI: fetch pages, render JS without Chromium, return clean Markdown over MCP.
Three things it does that a browser-driving tool doesn't — each measured head-to-head against Playwright MCP, Charlotte, Obscura, and Lightpanda on identical fixtures (full numbers, reproduce with make crossbench):
Installation goes through your MCP client rather than a global install: point it at ghcr.io/christopherdavenport/unblink on a container image and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Once Unblink is connected, these are the calls the assistant has available:
read — { url?, session?, use_current?, mode?, format?, selector?, max_tokens?, cursor?, wait_for?, wait_text?, wait_timeout?, headers?, auth? }browse — { url?, session?, use_current?, headers?, auth? }links — { url?, session?, use_current?, filter?, internal_only?, limit? }forms — { url?, session?, use_current? }find — { url?, session?, use_current?, query, max_hits? }site — { url?, session?, use_current? }click — { session, link_index? \submit_form — { session, form?, values?, files?, render? }controls — { url?, session?, use_current? }interact — { session, selector, event?, value?, key? }data — { url?, session?, use_current?, kind? }extract — { url?, session?, use_current?, root?, fields, limit? }The official MCP Go SDK requires Go ≥ 1.25. The Makefile sets GOTOOLCHAIN=auto, so the go command downloads the toolchain pinned in go.mod automatically — you do not need to install Go 1.25 yourself, and your global go env is left untouched. (If you run go directly rather than via make, prefix commands with GOTOOLCHAIN=auto.)
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. Unblink's toolset — read, browse, links and 11 more — is a fair guide to whether it matches your workflow. It is maintained by ChristopherDavenport; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Unblink's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| read | { url?, session?, use_current?, mode?, format?, selector?, max_tokens?, cursor?, wait_for?, wait_text?, wait_timeout?, headers?, auth? } |
| browse | { url?, session?, use_current?, headers?, auth? } |
| links | { url?, session?, use_current?, filter?, internal_only?, limit? } |
| forms | { url?, session?, use_current? } |
| find | { url?, session?, use_current?, query, max_hits? } |
| site | { url?, session?, use_current? } |
| click | { session, link_index? \ |
| submit_form | { session, form?, values?, files?, render? } |
| controls | { url?, session?, use_current? } |
| interact | { session, selector, event?, value?, key? } |
| data | { url?, session?, use_current?, kind? } |
| extract | { url?, session?, use_current?, root?, fields, limit? } |
| requests | { url?, session?, use_current? } |
| console | { url?, session?, use_current?, level? } |
{
"mcpServers": {
"unblink": {
"command": "docker",
"args": ["run", "-i", "--rm", "ghcr.io/christopherdavenport/unblink"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
The official MCP Go SDK requires Go ≥ 1.25. The Makefile sets GOTOOLCHAIN=auto, so the go command downloads the toolchain pinned in go.mod automatically — you do not need to install Go 1.25 yourself, and your global go env is left untouched. (If you run go directly rather than via make, prefix commands with GOTOOLCHAIN=auto.)
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.