head to head · open source
Browser Use vs vibe-check-mcp-server
Browser Use has 115,022 GitHub stars, 12,661 forks, 421 open issues and last shipped 3 days ago. vibe-check-mcp-server has 503 stars, 66 forks, 5 open issues and last shipped 7 days ago. Browser Use leads on adoption by 22,767% (115,022 vs 503 stars). Browser Use is written in Python under MIT; vibe-check-mcp-server is written in TypeScript under MIT. Browser Use has attracted 11% as many forks as stars, vibe-check-mcp-server 13%. Browser Use was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (ai-agents), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 8884 open source comparisons
Side by side
| Browser Use | vibe-check-mcp-server | |
|---|---|---|
| GitHub stars | ★ 115K | ★ 503 |
| License | MIT | MIT |
| Written in | Python | TypeScript |
| Last push | 2026-09-15 | 2026-09-11 |
| Forks | ⑂ 13K | ⑂ 66 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Browser Use if
- You weight community size — 115K stars and counting
- You want the MIT license terms
- Your stack matches Python
- You value the larger contributor base for long-term maintenance
pick vibe-check-mcp-server if
- You want the vibe-check-mcp-server feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and vibe-check-mcp-server fits your workflow better
About Browser Use
Browser Use is an open source Python library and hosted platform that enables AI agents to control web browsers programmatically. It lives in the AI agent and browser automation ecosystem, built on Playwright and designed to let LLMs interact with websites as a human would—clicking, filling forms, solving CAPTCHAs, and navigating dynamic interfaces. The project provides three deployment paths: a fully hosted cloud service, a command line interface for existing agents, and a local Python library for custom integrations.
read the full Browser Use overview →
About vibe-check-mcp-server
Vibe Check MCP This project is in maintenance mode. Active feature development has ended; only maintenance patches (security and bug fixes) are published. v2.9.0 is the latest maintenance release. The server remains fully functional. Community forks and contributions are welcome under the MIT license. KISS overzealous agents goodbye. Plug & play agent oversight tool. Based on research: In our study agents calling Vibe Check improved success +27% and halved harmful actions 41% Featured on PulseMCP “Most Popular (This Week)” • 5k+ monthly calls on Smithery.ai • research backed oversight • STDIO + streamable HTTP tr…
read the full vibe-check-mcp-server overview →
More in Productivity & Utilities
Related comparisons
More Automation projects
Compare either of these against the rest of the Automation field.
Frequently asked questions
Is Browser Use or vibe-check-mcp-server more popular?
Browser Use has 115,022 GitHub stars and vibe-check-mcp-server has 503. Browser Use has the larger community by that measure.
Are Browser Use and vibe-check-mcp-server free?
Both are open source. Browser Use is licensed under MIT and vibe-check-mcp-server under MIT. Neither carries a licence fee.
What is the difference between Browser Use and vibe-check-mcp-server?
Browser Use is written in Python and vibe-check-mcp-server in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, Browser Use or vibe-check-mcp-server?
Choose Browser Use if you want the larger community (115,022 stars) or its MIT licence terms. Choose vibe-check-mcp-server if its feature set, stack or MIT licence fits better. Both are self-hostable.