Steel Puppeteer

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Steel Puppeteer?

Steel Puppeteer is a Model Context Protocol server that provides browser automation capabilities using Puppeteer and Steel, allowing LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment.

how to use Steel Puppeteer?

To use Steel Puppeteer, configure it with the necessary environment variables, install dependencies, build the project, and start the server. You can then interact with the server through Claude Desktop or other compatible interfaces.

key features of Steel Puppeteer?

  • Browser automation with Puppeteer
  • Steel integration for 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
  • Local and remote Steel instance support

use cases of Steel Puppeteer?

  1. Automating web testing and scraping tasks.
  2. Capturing screenshots for documentation or analysis.
  3. Executing JavaScript for dynamic content manipulation.
  4. Interacting with web applications for data extraction.

FAQ from Steel Puppeteer?

  • Can Steel Puppeteer work with any web page?

Yes! Steel Puppeteer can automate interactions with most web pages that are accessible through a browser.

  • Is Steel Puppeteer free to use?

Yes! Steel Puppeteer is open-source and free to use.

  • What are the system requirements for running Steel Puppeteer?

Ensure you have Node.js installed and the necessary dependencies for Puppeteer.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Alloy

2 days ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

8 hours ago
Crevio

a day ago