### Local Development Setup for Steel MCP Server

Source: https://github.com/steel-dev/steel-mcp-server/blob/main/README.md

Steps to set up and run the Steel MCP Server locally for development. This involves cloning the repository, installing dependencies, building the project, and starting the server.

```bash
npm install
npm run build
npm start
```

--------------------------------

### Install Steel MCP Server via Smithery

Source: https://github.com/steel-dev/steel-mcp-server/blob/main/README.md

Command to install the Steel MCP Server for Claude Desktop using the Smithery CLI. This command automatically handles the client setup and installation process.

```bash
npx -y @smithery/cli install @steel-dev/steel-mcp-server --client claude
```

--------------------------------

### Clone, Install, and Build Steel MCP Server (Bash)

Source: https://github.com/steel-dev/steel-mcp-server/blob/main/README.md

Steps to clone the Steel MCP Server repository, install Node.js dependencies using npm, and build the project. This is a prerequisite for running the server.

```bash
git clone https://github.com/steel-dev/steel-mcp-server.git
cd steel-mcp-server
npm install
npm run build
```

--------------------------------

### Claude Desktop Steel Voyager Configuration

Source: https://github.com/steel-dev/steel-mcp-server/blob/main/README.md

Example JSON configuration for Claude Desktop to launch Steel Voyager. It specifies the command to run, arguments, and environment variables for different Steel modes (local or cloud). Adjust environment variables as needed for your setup.

```json
{
  "mcpServers": {
    "steel-puppeteer": {
      "command": "node",
      "args": ["path/to/steel-puppeteer/dist/index.js"],
      "env": {
        "STEEL_LOCAL": "false",
        "STEEL_API_KEY": "your_api_key_here"
      }
    }
  }
}
```

--------------------------------

### Steel MCP Server Tools and Configuration

Source: https://github.com/steel-dev/steel-mcp-server/blob/main/README.md

This section details the available tools for browser automation provided by the Steel MCP Server, including navigation, search, interaction (click, type), scrolling, history management, waiting, and screenshot capture. It also covers the server's configuration via environment variables for local or cloud operation.

```APIDOC
Steel MCP Server Tools:

- navigate
  - Description: Navigate to any URL in the browser.
  - Signature: navigate(url: string, required)
  - Parameters:
    - url (string, required): URL to navigate to (e.g. "https://example.com").

- search
  - Description: Perform a Google search by navigating to "https://www.google.com/search?q=encodedQuery".
  - Signature: search(query: string, required)
  - Parameters:
    - query (string, required): Text to search for on Google.

- click
  - Description: Click elements on the page using numbered labels.
  - Signature: click(label: number, required)
  - Parameters:
    - label (number, required): The label number of the element to click.

- type
  - Description: Type text into input fields using numbered labels.
  - Signature: type(label: number, required, text: string, required, replaceText?: boolean)
  - Parameters:
    - label (number, required): The label number of the input field.
    - text (string, required): Text to type into the field.
    - replaceText (boolean, optional): If true, replaces any existing text in the field.

- scroll_down
  - Description: Scroll down the page.
  - Signature: scroll_down(pixels?: integer)
  - Parameters:
    - pixels (integer, optional): Number of pixels to scroll down. If not specified, scrolls by one full page.

- scroll_up
  - Description: Scroll up the page.
  - Signature: scroll_up(pixels?: integer)
  - Parameters:
    - pixels (integer, optional): Number of pixels to scroll up. If not specified, scrolls by one full page.

- go_back
  - Description: Navigate to the previous page in browser history.
  - Signature: go_back()
  - Parameters: None.

- wait
  - Description: Wait for up to 10 seconds, useful for pages that load slowly or need more time for dynamic content to appear.
  - Signature: wait(seconds: number, required)
  - Parameters:
    - seconds (number, required): Number of seconds to wait (0 to 10).

- save_unmarked_screenshot
  - Description: Capture the current page without bounding boxes or highlights and store it as a resource.
  - Signature: save_unmarked_screenshot(resourceName?: string)
  - Parameters:
    - resourceName (string, optional): Name to store the screenshot under (e.g. "before_login"). If omitted, a generic name is generated automatically.

Steel MCP Server Resources:

- Screenshots:
  - Description: Saved screenshots are accessible via an MCP resource URI in the form of: `screenshot://RESOURCE_NAME`.
  - Access: Retrieved through a standard MCP resource retrieval request.

Steel MCP Server Configuration:

- STEEL_LOCAL
  - Default: "false"
  - Description: Determines if Steel Voyager runs in local (true) or cloud (false) mode.

- STEEL_API_KEY
  - Default: (none)
  - Description: Required only when STEEL_LOCAL = "false". Used to authenticate requests with the Steel endpoint.

- STEEL_BASE_URL
  - Default: "https://api.steel.dev"
  - Description: The base URL for the Steel API. Override this if self-hosting the Steel server. If STEEL_LOCAL = "true" and STEEL_BASE_URL is unset, it defaults to "http://localhost:3000".

- GLOBAL_WAIT_SECONDS
  - Default: (none)
  - Description: Optional. Number of seconds to wait after each tool action (for instance, to allow slow-loading pages).
```

--------------------------------

### Claude Desktop Configuration for Local Steel

Source: https://github.com/steel-dev/steel-mcp-server/blob/main/README.md

JSON configuration for Claude Desktop to connect to a local or self-hosted Steel instance. It sets the STEEL_LOCAL environment variable to true and specifies the STEEL_BASE_URL for the connection.

```json
{
  "mcpServers": {
    "steel-puppeteer": {
      "command": "node",
      "args": ["path/to/steel-voyager/dist/index.js"],
      "env": {
        "STEEL_LOCAL": "true",
        "STEEL_BASE_URL": "http://localhost:3000",
        "GLOBAL_WAIT_SECONDS": "1"
      }
    }
  }
}
```

--------------------------------

### Configure Steel Local Mode

Source: https://github.com/steel-dev/steel-mcp-server/blob/main/README.md

Sets environment variables for running Steel in local mode. `STEEL_LOCAL` should be 'true', and `STEEL_BASE_URL` can optionally point to a custom Steel server. No API key is needed in this mode.

```bash
export STEEL_LOCAL="true"
export STEEL_BASE_URL="http://localhost:3000" # only if overriding
```

--------------------------------

### Claude Desktop Configuration for Steel Cloud

Source: https://github.com/steel-dev/steel-mcp-server/blob/main/README.md

JSON configuration for Claude Desktop to connect to the Steel MCP server in cloud mode. It specifies the command to run the server and environment variables like the API key and cloud mode flag.

```json
{
  "mcpServers": {
    "steel-puppeteer": {
      "command": "node",
      "args": ["path/to/steel-voyager/dist/index.js"],
      "env": {
        "STEEL_LOCAL": "false",
        "STEEL_API_KEY": "YOUR_STEEL_API_KEY_HERE",
        "GLOBAL_WAIT_SECONDS": "1"
      }
    }
  }
}
```

--------------------------------

### Configure Steel Cloud Mode

Source: https://github.com/steel-dev/steel-mcp-server/blob/main/README.md

Sets environment variables for running Steel in cloud mode. `STEEL_LOCAL` should be 'false', and `STEEL_API_KEY` is required for authentication with the Steel cloud service. `STEEL_BASE_URL` defaults to `https://api.steel.dev`.

```bash
export STEEL_LOCAL="false"
export STEEL_API_KEY="YOUR_STEEL_API_KEY_HERE"
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.