Steel Puppeteer MCP server

Integrates AI with web browsers through Puppeteer and Steel's automation platform, enabling complex web tasks, data scraping, and workflow automation.
Back to servers
Setup instructions
Provider
rdvo
Release date
Dec 05, 2024
Language
TypeScript
Stats
1 star

This MCP server enables large language models to control a web browser through Puppeteer, allowing them to navigate websites, take screenshots, and interact with web elements. It integrates with Claude Desktop to provide browser automation capabilities.

Installation

Prerequisites

  • Node.js installed on your system
  • Claude Desktop (for integration with Claude)

Setting Up Steel Puppeteer

  1. Install the dependencies:
npm install
  1. Build the project:
npm run build
  1. Start the server:
npm start

Configuration

Claude Desktop Integration

To use Steel Puppeteer with Claude Desktop, add this configuration to your Claude Desktop config file (typically at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

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

Replace path/to/steel-puppeteer/dist/index.js with the actual path to the compiled JavaScript file on your system.

Environment Variables

Configure Steel Puppeteer using these environment variables:

  • STEEL_LOCAL (optional, default: "false"): Set to "true" to use a local Steel instance
  • STEEL_API_KEY (required if using cloud service): Your Steel API key
  • STEEL_URL (optional): Custom Steel instance URL if not using the default

You can set these directly in your shell or create a .env file in the project root.

Local Steel Instance

STEEL_LOCAL=true

Cloud Steel Service

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

Available Tools

Navigation

Navigate to any URL in the browser:

puppeteer_navigate

Parameters:

  • url (string, required): URL to navigate to
  • timeout (number, optional, default: 60000): Navigation timeout in milliseconds
  • waitUntil (string, optional, default: "domcontentloaded"): When to consider navigation succeeded. Options: "load", "domcontentloaded", "networkidle0", "networkidle2"

Screenshots

Capture screenshots of the entire page or specific elements:

puppeteer_screenshot

Parameters:

  • name (string, required): Name for the screenshot
  • selector (string, optional): CSS selector for element to screenshot

Page Interactions

Click Elements

puppeteer_click

Parameter: selector (string, required): CSS selector for element to click

Fill Form Fields

puppeteer_fill

Parameters:

  • selector (string, required): CSS selector for input field
  • value (string, required): Value to fill

Select Dropdown Option

puppeteer_select

Parameters:

  • selector (string, required): CSS selector for element to select
  • value (string, required): Value to select

Hover Over Elements

puppeteer_hover

Parameter: selector (string, required): CSS selector for element to hover

Content and Scripting

Execute JavaScript

puppeteer_evaluate

Parameter: script (string, required): JavaScript code to execute

Extract Page Content

puppeteer_get_content

Parameter: selector (string, optional): CSS selector to get content from specific elements. If not provided, returns whole page content

Scroll the Page

puppeteer_scroll

Parameters:

  • scrollDelay (number, optional, default: 100): Delay between scrolls in milliseconds
  • maxScrolls (number, optional, default: 50): Maximum number of scrolls

Accessing Resources

The server provides access to two types of resources:

Console Logs

Access browser console output:

console://logs

Screenshots

View captured screenshots:

screenshot://<name>

Where <name> is the name specified when taking the screenshot.

Troubleshooting

  • Puppeteer Issues: Ensure necessary system dependencies are installed. Check the Puppeteer troubleshooting guide.
  • Steel API Key: Verify your API key is valid if using the cloud service.
  • Local Steel Instance: Confirm it's running and accessible at the specified URL.

How to install this MCP server

For Claude Code

To add this MCP server to Claude Code, run this command in your terminal:

claude mcp add-json "steel-puppeteer" '{"command":"node","args":["path/to/steel-puppeteer/dist/index.js"],"env":{"STEEL_LOCAL":"true"}}'

See the official Claude Code MCP documentation for more details.

For Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

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

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.

For Claude Desktop

To add this MCP server to Claude Desktop:

1. Find your configuration file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json

2. Add this to your configuration file:

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

3. Restart Claude Desktop for the changes to take effect

Want to 10x your AI skills?

Get a free account and learn to code + market your apps using AI (with or without vibes!).

Nah, maybe later