puppeteer_navigate
Navigate to any URL in the browser
urlrequiredlaunchOptionsallowDangerous
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 7, 2026
Browser automation: navigate, click, fill, screenshot and evaluate in a headless browser.
A local stdio MCP server that gives an assistant headless-browser tools: navigate, click, hover, fill, select, screenshot and run JavaScript.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
Browser automation through a headless browser page, as a CLI and a stdio MCP server in one bin. Navigate to a URL, click, hover, fill and select form elements, take named screenshots and evaluate JavaScript in the page.
The browser itself sits behind an injectable executor interface
(BrowserExecutor 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 Puppeteer-compatible executor to drive a real browser.
Launch options that weaken browser security (--no-sandbox,
--disable-web-security, --allow-insecure-localhost) are
rejected unless a call explicitly passes allowDangerous: true.
Exit codes: 0 success, 1 browser error, 2 usage error.
MCP client config:
MIT license.
Source: README.md at commit df67cb3
Navigate to any URL in the browser
urlrequiredlaunchOptionsallowDangerousCapture screenshots of the entire page or specific elements
namerequiredwidthheightencodedselectorClick elements on the page
selectorrequiredHover elements on the page
selectorrequiredFill out input fields
valuerequiredselectorrequiredSelect an element with a SELECT tag
valuerequiredselectorrequiredExecute JavaScript in the browser console
scriptrequired90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
npx -y @reneturcios/headlessstage mcpheadlessstage mcp # stdio MCP serverheadlessstage navigate <url>headlessstage screenshot <name> [selector]headlessstage click <selector>headlessstage fill <selector> <value>headlessstage evaluate <script>headlessstage --version{ "mcpServers": { "headlessstage": { "command": "npx", "args": ["-y", "@reneturcios/headlessstage", "mcp"] } }}docker run -i ghcr.io/cloudcorprecords/headlessstage # MCP serverdocker run --rm ghcr.io/cloudcorprecords/headlessstage --versionnpm installnpm run buildnpm test