rdvo_mcp-server

Steel Puppeteer is a powerful server designed to facilitate browser automation through the integration of Puppeteer and Steel. It allows Language Model Models (LLMs) to perform various web interactions such as navigation, clicking, form filling, and content extraction. The server supports both local and remote Steel instances, providing flexibility in deployment. With features like console log monitoring, screenshot capturing, and JavaScript execution, Steel Puppeteer is ideal for tasks that require real-time browser interaction. It also supports lazy-loading through scrolling, making it suitable for dynamic web pages. The server can be configured using environment variables and is compatible with platforms like Claude Desktop, where it can be easily integrated through configuration files. Whether for testing, data extraction, or automation, Steel Puppeteer offers a comprehensive solution for browser-based tasks.

Features

• Browser automation with Puppeteer
• Steel integration for browser session management
• Console log monitoring and capture
• Screenshot capabilities
• JavaScript execution

MCP Tools

• {'puppeteer_navigate': 'Navigate to any URL in the browser'}
• {'puppeteer_screenshot': 'Capture screenshots of the entire page or specific elements'}
• {'puppeteer_click': 'Click elements on the page'}
• {'puppeteer_fill': 'Fill out input fields'}
• {'puppeteer_select': 'Select an element with SELECT tag'}
• {'puppeteer_hover': 'Hover elements on the page'}
• {'puppeteer_evaluate': 'Execute JavaScript in the browser console'}
• {'puppeteer_get_content': 'Extract content from the current page'}
• {'puppeteer_scroll': 'Scroll the page to trigger lazy-loading'}

MCP Resources

• {'Console Logs': 'Browser console output in text format'}
• {'Screenshots': 'PNG images of captured screenshots'}

Usage with Different Platforms

Claude Desktop Configuration

{
  "mcpServers": {
    "steel-puppeteer": {
      "command": "node",
      "args": ["path/to/steel-puppeteer/dist/index.js"],
      "env": {
        "STEEL_LOCAL": "true"
      }
    }
  }
}

Server Configuration

STEEL_LOCAL=true


If you're using the Steel cloud service, your `.env` file would look like this:


STEEL_API_KEY=your-steel-api-key
STEEL_LOCAL=false

Running the Server

npm install
npm run build
npm start