Blog

Skip the Browser from Claude Desktop

Unbrowse is now a real MCP server. One JSON block in your config and your agent gets the web - without a browser.

Lewis Tham
April 5, 2026

Skip the Browser from Claude Desktop

Unbrowse is now a real MCP server. One JSON block in your config and your agent gets the web - without a browser.

Published 2026-04-05

Unbrowse reverse-engineers the APIs behind any website and turns them into reusable skills that agents can call directly. Instead of spinning up a headless browser, waiting for renders, and parsing DOM, your agent resolves an intent against Unbrowse's shared marketplace and gets structured API responses back.

Starting with v2.12, unbrowse mcp is a proper stdio MCP server. It speaks JSON-RPC 2.0, implements initialize, tools/list, and tools/call, and works with any MCP host: Claude Desktop, Cursor, Codex, Windsurf, or anything else that can spawn a stdio process.

Setup

Add this to your MCP host config:

{
  "mcpServers": {
    "unbrowse": {
      "command": "npx",
      "args": ["-y", "unbrowse", "mcp"]
    }
  }
}

For Claude Desktop, that file lives at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS.

For Cursor, add it in Settings > MCP Servers.

For Codex and Windsurf, add the same block to whichever config file your host reads.

What happens when you use it

Without Unbrowse: your agent opens a headless browser, waits for the page to render, clicks around, parses HTML, maybe gets rate-limited, burns tokens on DOM extraction, and takes 30-60 seconds per site interaction.

With Unbrowse: your agent calls unbrowse_resolve with an intent and a URL. If a skill already exists in the marketplace, it resolves instantly. If not, Unbrowse captures the site once, learns the real API endpoints, publishes a reusable skill, and returns structured data. The next agent that hits the same site gets the fast path.

Every response now includes machine-readable impact data: time saved, tokens saved, browser avoided, and suggested next action. Your agent can reason about whether to browse or route on a per-request basis with real numbers.

The tools your agent gets

Once connected, your MCP host sees these tools:

  • unbrowse_resolve - find or learn the API behind a site for a given intent
  • unbrowse_execute - call a resolved endpoint with parameters
  • unbrowse_search - search the skill marketplace across all domains
  • unbrowse_health - check that the local runtime is up
  • unbrowse_login - interactive auth for gated sites

There is also a full browser tool chain for first-time capture on sites that have not been indexed yet. But most of the time, resolve + execute is all you need.

What is next

The MCP surface today is tools-only. Resources and prompts are coming. The marketplace already has 8,760 indexed endpoints across 98 domains. Every agent that uses Unbrowse makes the network better for the next one.

Try it: add the config block, restart your host, and ask your agent to do something on a website.