Steel Puppeteer logo

Steel Puppeteer

by MCP-Mirror

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.

View on GitHub

Last updated: N/A

What is Steel Puppeteer?

Steel Puppeteer is an MCP server that leverages Puppeteer and Steel to provide browser automation for LLMs. It allows LLMs to navigate web pages, capture screenshots, interact with elements, and execute JavaScript within a real browser environment.

How to use Steel Puppeteer?

To use Steel Puppeteer, configure it within Claude Desktop or run it independently. Install dependencies with npm install, build the project with npm run build, and start the server with npm start. Configure environment variables like STEEL_LOCAL and STEEL_API_KEY as needed. Access browser console logs via console://logs and screenshots via screenshot://<name>.

Key features of Steel Puppeteer

  • Browser automation with Puppeteer

  • Steel integration for browser session management

  • Console log monitoring and capture

  • Screenshot capabilities

  • JavaScript execution

  • Basic web interaction (navigation, clicking, form filling)

  • Content extraction with token limit handling

  • Lazy-loading support through scrolling

Use cases of Steel Puppeteer

  • Automated web scraping

  • LLM-driven web interaction

  • Web-based task automation

  • Screenshot generation for documentation

  • Web application testing

FAQ from Steel Puppeteer

How do I configure Steel Puppeteer with Claude Desktop?

Add a configuration block to your Claude Desktop config file (~/Library/Application Support/Claude/claude_desktop_config.json on macOS) specifying the command, arguments, and environment variables for the server.

What environment variables are required?

STEEL_LOCAL is optional (default: "false"). If STEEL_LOCAL is "false", STEEL_API_KEY is required. STEEL_URL is optional for custom Steel deployments.

How do I access console logs?

Console logs are available via the console://logs resource.

How do I access screenshots?

Screenshots are accessible via the screenshot://<name> resource, where <name> is the name specified when capturing the screenshot.

What if I encounter issues with Puppeteer?

Ensure that you have the necessary dependencies installed on your system. Refer to the Puppeteer troubleshooting guide for more information.