What environment variables are required?
`STEEL_LOCAL` (optional, default "false"): set to "true" for local Steel instance. `STEEL_API_KEY` required only if `STEEL_LOCAL` is "false". `STEEL_URL` optional for custom Steel deployment.
@MCP-Mirror
Basic information
Mirror of
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"steel-puppeteer": {
"command": "node",
"args": [
"path/to/steel-puppeteer/dist/index.js"
],
"env": {
"STEEL_LOCAL": "true"
}
}
}
}Navigate to any URL in the browser
Capture screenshots of the entire page or specific elements
Click elements on the page
Fill out input fields
Select an element with SELECT tag
Hover elements on the page
Execute JavaScript in the browser console
Extract content from the current page
Scroll the page to trigger lazy-loading
Steel Puppeteer is a Model Context Protocol server that provides browser automation capabilities using Puppeteer and Steel. It enables LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment.
Install dependencies with npm install, build with npm run build, and start the server with npm start. Configure it for Claude Desktop by adding a steel-puppeteer entry to claude_desktop_config.json with the compiled index.js path and appropriate environment variables (STEEL_LOCAL, STEEL_API_KEY, STEEL_URL).
`STEEL_LOCAL` (optional, default "false"): set to "true" for local Steel instance. `STEEL_API_KEY` required only if `STEEL_LOCAL` is "false". `STEEL_URL` optional for custom Steel deployment.
Install dependencies (`npm install`), build (`npm run build`), then start (`npm start`). If using a local Steel instance, set `STEEL_LOCAL=true` in a `.env` file.
It provides nine tools: `puppeteer_navigate`, `puppeteer_screenshot`, `puppeteer_click`, `puppeteer_fill`, `puppeteer_select`, `puppeteer_hover`, `puppeteer_evaluate`, `puppeteer_get_content`, and `puppeteer_scroll`.
Two resource types: console logs (`console://logs`) for browser console output, and screenshot images (`screenshot://<name>`) captured during sessions.
Allow LLMs to control a browser with Browserbase and Stagehand
This MCP server provides browser automation capabilities through Puppeteer, allowing interaction with both new browser instances and existing Chrome windows.
BitBrowser MCP simple to use, no complicated procedures required. Supports a variety of intelligent agent services.
MCP server for fetch web page content using Playwright headless browser.
Comments