io.github.CloudCorpRecords/browserstage
Automate a browser with accessibility snapshots: navigate, click, type, fill and wait.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
@reneturcios/browserstageclaude mcp add browserstage -- npx -y @reneturcios/browserstage@0.1.0 mcp
{
"mcpServers": {
"browserstage": {
"command": "npx",
"args": [
"-y",
"@reneturcios/browserstage@0.1.0",
"mcp"
]
}
}
}
ghcr.io/cloudcorprecords/browserstage:0.1.0claude mcp add browserstage -- docker run -i --rm ghcr.io/cloudcorprecords/browserstage:0.1.0 mcp
{
"mcpServers": {
"browserstage": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/cloudcorprecords/browserstage:0.1.0",
"mcp"
]
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
browserstage
Snapshot-driven browser automation as a CLI and a stdio MCP server in one bin. Navigate, capture an accessibility snapshot of the page, then act on elements by the references in that snapshot: click, hover, drag, drop, type, fill whole forms, select options, press keys, upload files and handle dialogs. Console messages and network requests are readable tools, and tabs can be listed, created, closed and selected.
The browser sits behind an injectable executor interface
(StageBrowser in src/types.ts). This package bundles no browser
and downloads none: with no executor configured, browser commands
fail with a clear "Browser unavailable" error. Deployments inject
a Playwright-compatible executor to drive a real browser. The
browser_run_code_unsafe tool runs arbitrary code against the
page in the original design and keeps that name and its warning
here: only enable it where you would run arbitrary code yourself.
Install
npx -y @reneturcios/browserstage mcp
CLI
browserstage mcp
browserstage navigate <url>
browserstage snapshot
browserstage press <key>
browserstage resize <width> <height>
browserstage --version
Exit codes: 0 success, 1 browser error, 2 usage error.
MCP tools
24 core tools: browser_navigate, browser_navigate_back,
browser_snapshot, browser_find, browser_click,
browser_hover, browser_drag, browser_drop,
browser_select_option, browser_type, browser_press_key,
browser_fill_form, browser_take_screenshot,
browser_run_code_unsafe, browser_evaluate, browser_wait_for,
browser_handle_dialog, browser_file_upload,
browser_console_messages, browser_network_requests,
browser_network_request, browser_tabs, browser_close,
browser_resize.
MCP client config:
{
"mcpServers": {
"browserstage": {
"command": "npx",
"args": ["-y", "@reneturcios/browserstage", "mcp"]
}
}
}
Docker
docker run -i ghcr.io/cloudcorprecords/browserstage # MCP server
docker run --rm ghcr.io/cloudcorprecords/browserstage --version
Development
npm install
npm run build
npm test
MIT license.
Frequently asked questions
What is io.github.CloudCorpRecords/browserstage?
Automate a browser with accessibility snapshots: navigate, click, type, fill and wait.
How do I install io.github.CloudCorpRecords/browserstage?
It runs on your machine. In Claude Code: claude mcp add browserstage -- npx -y @reneturcios/browserstage@0.1.0 mcp. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.CloudCorpRecords/browserstage need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is io.github.CloudCorpRecords/browserstage open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains io.github.CloudCorpRecords/browserstage?
It is published by CloudCorpRecords. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.