MCP Server Browser runs on your own machine — the client starts it, so there is no endpoint to ping. 879 installs a week from npm. Last commit 9 Oct 2026.
MCP server for browser use access
We read the source, 2 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
'data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAEsAAABfCAYAAACgCTpnAAAAAXNSR0IArs4c6QAAAERlWElmTU0AKgAAAAgAAYdpAAQAAAABAAAAGgAAAAAAA6ABAAMAAAABAAEAAKACAAQAAAABAAAAS6ADAAQAAAABAAAAXwAAAAARa1b5AAAaTElEQVR4AeVcB7iUxbme3T2FKl1BlKZgFDWo2JCiPCpgohQBsRB7iTwmJrZriD0RSACDBb3Gq6i5sWCEq6K…
const statA = fs.statSync(path.join(logDir, a));
this.logger = logger.spawn(this.constructor.name);
'process.env.UI_TARS_APP_PRIVATE_KEY_BASE64': JSON.stringify(
process.env.UI_TARS_APP_PRIVATE_KEY_BASE64,
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp-server-browser -- npx -y @agent-infra/mcp-server-browser
{
"mcpServers": {
"mcp-server-browser": {
"command": "npx",
"args": [
"-y",
"@agent-infra/mcp-server-browser"
]
}
}
}
[mcp_servers.mcp-server-browser]
command = "npx"
args = ["-y", "@agent-infra/mcp-server-browser"]
{
"mcpServers": {
"mcp-server-browser": {
"command": "npx",
"args": [
"-y",
"@agent-infra/mcp-server-browser"
]
}
}
}
{
"servers": {
"mcp-server-browser": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@agent-infra/mcp-server-browser"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
DISPLAY (DISPLAY environment variable for browser rendering).
MCP server for browser automation with AI agent
MCP server for AI web browser automation using Browserbase and Stagehand
MCP server for browser automation via Vercel's agent-browser CLI
MCP server for Zen Browser automation via WebDriver BiDi
BrowserStack's Official MCP Server
MCP server for parallel browser automation across multiple providers.
Zenrows MCP server: Fetch, Extract, Batch, and Browser Sessions for AI agents
MCP server + Chrome extension for AI browser control with real sessions.
Answers built from our own checks of this server.