neobrowser
Enables automation of browser-dependent workflows—web scraping, testing, compliance checks—without detection evasion friction.
MCP server that drives real Chrome with your real logged-in sessions — genuine fingerprint (passes bot.sannysoft), human-like input, bot-wall aware. 43 tools, single static Rust binary.
- Automate testing web applications with real browser sessions and logged-in user accounts.
- Scrape data from websites that require authentication and detect bot activity.
- Generate screenshots and PDFs of web pages as they appear to actual users with real sessions.
Enables automation of browser-dependent workflows—web scraping, testing, compliance checks—without detection evasion friction. Preserves authentication state and fingerprint integrity, reducing engineering overhead for legitimate bot detection bypass.
Backend teams automating authenticated web interactions, QA engineers validating browser-dependent flows, data engineers scraping protected endpoints.
https://github.com/pitiflautico/neobrowser
By pitiflautico
How to Get It
claude plugins install pitiflautico/neobrowser
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me automate testing web applications with real browser sessions and logged-in user accounts
Trust Signals Auto-scanned
Community Pulse New
- NeoBrowser: An MCP server that drives real Chrome with your logged-in sessions — Hacker News · 33 pts
- Mighty and the Neobrowsers — Hacker News · 1 pts
2 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 92 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
- Single maintainer. Consider the risk if this person stops maintaining the project.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 92 GitHub stars; contributors unknown; last commit 0d ago; license MIT.