Neobrowser
MCP server that drives real Chrome with your real logged-in sessions — genuine fingerprint (passes bot.sannysoft), human
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.
Setup and access
Check the connection method, access level, and compatible clients before enabling the server.
- Transport
- stdio
- Authentication
- Varies
- Registry status
- Active
- Last updated
- Aug 22, 2026
Connects to external tools and data. Use the least-privileged credentials and access scope that support your workflow.
Related mcp servers
Other listings in the same category or with overlapping tags.
Awesome MCP Servers
A collection of MCP servers.
Headroom
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95%
Context7
Current, version-specific library documentation in every prompt.
FAQ
- What does Neobrowser MCP do?
- 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.
- How do I connect Neobrowser MCP?
- Follow the stdio setup in the source repo, then confirm permissions before you enable it.
- Does Neobrowser MCP require authentication?
- It depends on the capability you enable. Check the setup notes for the exact service path.
- Who maintains Neobrowser MCP?
- pitiflautico publishes this implementation. Check the source repo for maintainers and releases.
- Where is the Neobrowser source?
- Source and updates: https://github.com/pitiflautico/neobrowser