Show HN: Turbo-Browser-MCP – Batch forms, DOM deltas and submit guards for MCP

lubujackson 3 hours ago | parent | next [-]

Whoa, this looks incredible.

Having built my company's MCP server, I have a deeper appreciation for how important well-defined tools can be. It is clear to me that tool availability and coordination is going to be a top (or THE top) focus in the near future, more important than the model itself.

If you ever look at how an LLM greps through a codebase, pulling small slices at a time to gather what it needs, you have a sense of how precise tools can broaden a model's capabilities. If I had today's Sonnet with tooling from 5 years in the future, I expect it would beat Fable 5.2 hands down - that's how dramatic the difference is.

Anthropic/OpenAI have really buried the lede about tooling, baking it into their harnesses and trying to force lock-in. We are still in the AOL days of the internet right now.

▲

snake_doc 3 hours ago | parent | prev [-]

Hmm you should really benchmark against

https://github.com/browser-use/browser-harness https://github.com/anomalyco/browse https://github.com/vercel-labs/agent-browser

The answer is very likely not a MCP server. browse (anomalyco) is relatively new; but the other 2 are battle tested in production….

▲

vidarh an hour ago | parent | next [-]

Does any of these handle the case where the site needs you to pass a bot detection that fails if the browser is remote controlled and so need a human to access the same profile via a non-remote controlled browser first?

That's what's stopping me from using most of these things instead of just having the agent drive a browser directly with lower level integrations.

▲

lukevp 2 hours ago | parent | prev [-]

None of these do the same thing as the posted MCP. It’s about batching and diff/deltas to reduce token usage and latency.

	▲	snake_doc 2 hours ago \| parent [-]
		Benchmark for the end 2 end browser tasks…. The other options operate at a different level of abstraction where the actions space also reduce token usage and latency…