So I built WebBridge (yes - not so fancy name there). (Well - Claude built it. I directed. Like every PM does.)
What it actually does:
1. You install a Chrome extension 2. You browse to a site you're logged into - your library, your lab results portal, whatever 3. You click Record, do the thing you want to automate, click Stop 4. Claude reads the captured API traffic and generates a permanent MCP server 5. That server works with any MCP client - Claude (Cowork/Code), Cursor, VS Code, Windsurf, Cline, you name it
The whole thing takes about 10 minutes. No code written by you.
This is for non-tech folks who live inside AI providers, who just want to use it and move on. Legal analysts, market researchers, market watchers, marketing and competitive intelligence, and anyone who wants to use a specific website for a specific purpose, repeatedly.
The README has some use cases showcased: "Public Library Search" and "Legal Compliance Auditing."
There may not be an exact equivalent anywhere to what I purpose-built. I'd welcome being proven wrong on that.
Feedback is welcome - that's why I'm posting.
thebuilderjr•3h ago
nonstopnonsense•17m ago
The API drift is something I need to think about. They are bound to change over time - webbridge_update was made for that for now.
I am not entirely understanding "over fitting", can you please explain more?