Open-source tool turns a site into an MCP by recording the browser

Name: Open-source tool turns a site into an MCP by recording the browser
Availability: InStock
Author: ethantheswe

by ethantheswe·Mar 7, 2026·1 point·0 comments

Visit Project View on HN

AI Analysis

●●●BangerBig BrainShip ItSolve My Problem

Browser-to-MCP automation beats manual API wrapping; auto-generates TypeScript servers with zero config.

Strengths

•Captures real network traffic instead of guessing endpoints—eliminates manual API reverse-engineering work.
•Handles auth token detection and refresh tooling, not just dumb endpoint mapping.
•LLM refinement pass actually improves tool descriptions instead of shipping raw garbage.

Weaknesses

•Early-stage (admits 'vibe coded'), missing error handling for complex auth flows like OAuth.
•Unclear how it handles rate-limiting, pagination, or stateful multi-step workflows.

Post Description

Built browse2mcp to automatically create an mcp server by opening a broswer. I built it because there's a few website's I use on a regular basis that were super annoying to try to get to work with Claude. Note: this is mostly vibe coded with a few touch ups.

How it works:

Run browse2mcp to record and a browser opens, you use the site normally

Close the browser, all API requests are saved

Run browse2mcp generate, it analyzes the traffic and spits out a TypeScript MCP server you can have it automatically run add to claude desktop

It handles REST and GraphQL, detects auth patterns, bakes in captured tokens, and generates a login tool so you can refresh expired tokens without rerecording.

There's also an optional LLM refinement pass using Claude Haiku (could probably extend to other models) that rewrites the autogenerated tool descriptions into something actually useful, adds sensible defaults, and removes noisy endpoints.

Some things definitely still to-do are to decrease the tools (it doesn't consolidate very well), and make it generally less flaky.

https://github.com/danielthedm/browse2mcp