AdYour product here, seen by people installing AI tools every day Sponsor slots open: 12 of 12, from $249 a month

Engine vs browser-use

Engine and browser-use are both browser automation MCP servers. browser-use scores higher (100 vs 82 out of 100). browser-use has more GitHub stars (119k), and Engine was updated more recently (2 days ago). The table compares them side by side.

Enginebrowser-use
Score82 / 100100 / 100
What it doesWeaveKit engine — a metadata-driven headless backend runtime with Git-versioned metadataBrowser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
PublisherVerified: npm:@weave-kitVerified: browser-use.com
GradesMaintenance A, Licence A, Quality CMaintenance A, Licence A, Quality A
npm downloads a week1,357Not on npm
RunsLocalLocal and remote
Works withClaude Code, Claude Desktop, Cursor, Codex, Gemini CLI, VS Code, WindsurfClaude Code, Claude Desktop, Cursor, Codex, Gemini CLI, VS Code, Windsurf
GitHub stars0118,527
Last commit20 Oct 202617 Oct 2026
LicenceMITMIT
Listed since20 Oct 202619 Oct 2026
Install EngineInstall browser-use

Questions

Is Engine or browser-use more popular?

browser-use has more GitHub stars: 118,527.

Can I use Engine and browser-use together?

Yes. AI assistants can load several MCP servers at once. Install both and the assistant picks the right one for each task.