MCP server adapter for Obscura Rust headless browser — web scraping with anti-detection.
Obscura MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Obscura MCP directly instead of describing what you should do. MCP server adapter for Obscura Rust headless browser — web scraping with anti-detection.
An MCP server adapter for Obscura, a lightweight Rust headless browser for scraping and AI agent automation.
Once Obscura MCP is connected, these are the calls the assistant has available:
urls — string[]eval — stringconcurrency — numbertimeout — numberYou will need 2 environment variables: OBSCURA_PATH, MCP_HTTP_HOST. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
obscura-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Obscura MCP's toolset — urls, eval, concurrency and 1 more — is a fair guide to whether it matches your workflow. It is maintained by Metadrama; 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 |
|---|---|
| urls | string[] |
| eval | string |
| concurrency | number |
| timeout | number |
{
"mcpServers": {
"obscura-mcp": {
"command": "obscura-mcp",
"args": ["--transport", "stdio"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| OBSCURA_PATH | Filesystem location the server is allowed to use. | Optional |
| MCP_HTTP_HOST | Endpoint or connection string the server talks to. | 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.