auto-browser

Name: auto-browser
Author: LvcidPsyche

[![LvcidPsyche/auto-browser MCP server](https://glama.ai/mcp/servers/LvcidPsyche/auto-browser/badges/score.svg)](https://glama.ai/mcp/servers/LvcidPsyche/auto-…

Browser Automation

auto-browser is a community MCP server that connects AI assistants like Claude to [![lvcidpsyche/auto-browser mcp server](https://glama.ai/mcp/servers/lvcidpsyche/auto-browser/badges/score.svg)](https://glama.ai/mcp/servers/lvcidpsyche/auto-…. It runs locally on your machine, keeping your data private and giving you full control over the connection. Adding it to your setup expands what Claude can do without any extra coding.

About auto-browser

Overview

🐍 🏠 🐧 🍎 🪟 - Open-source MCP-native browser agent with human takeover via noVNC, reusable auth profiles, and approval/audit rails. Playwright + FastAPI, Docker-based isolated sessions, stdio bridge for Claude Desktop and Cursor.

Topics

mcp-server

Who Should Use auto-browser?

1Extend Claude and other AI assistants with new capabilities
2Automate tasks that previously required manual steps
3Connect your existing tools to an AI workflow
4Reduce repetitive work by letting AI interact with your services

How auto-browser Compares

✦It runs entirely on your local machine, so no data leaves your environment — important for teams with privacy or compliance requirements.

✦Compared to other Browser Automation MCP servers, it focuses on a well-scoped set of capabilities, which keeps the integration lightweight and predictable.