Rod

Provides a Rod-based MCP server for browser automation to interact with web pages via LLMs.
  • go

27

GitHub Stars

go

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "go-rod-rod-mcp": {
      "command": "rod-mcp",
      "args": [
        "-c",
        "rod-mcp.yaml"
      ]
    }
  }
}

Rod MCP Server enables browser automation capabilities powered by Rod, exposing a programmable interface that lets you control web pages through an MCP client. This makes it easy to perform actions like clicking elements, taking screenshots, and generating PDFs in an automated workflow driven by language models or other automation tools.

How to use

You run the Rod MCP Server locally and connect an MCP client to it. The server exposes tools for browser automation, allowing you to click elements, capture screenshots, create PDFs, and more. Start the server with your chosen configuration, then send commands via the MCP client to perform web interactions and retrieve results.

How to install

Prerequisites and setup are straightforward. You need Go 1.23 or higher and a Chrome/Chromium browser. Follow these steps to get up and running.

Step 1: Clone the Rod MCP project and enter the directory.

git clone https://github.com/go-rod/rod-mcp.git
cd rod-mcp

Step 2: Install dependencies.

go mod tidy

Step 3: Build the project.

go build

Step 4: Start the MCP server using the provided configuration. The server can be run in a local (stdio) mode with a config file that points to theRod MCP executable.

rod-mcp -c rod-mcp.yaml

Configuration

Configure the Rod MCP Server for how it should run and where it should place browser data.

The configuration file supports the following options:

  • serverName: Server name, default is "Rod Server"
  • browserBinPath: Browser executable file path, use system default browser if empty
  • headless: Whether to run the browser in headless mode, default is false
  • browserTempDir: Browser temporary file directory, default is "./rod/browser"
  • noSandbox: Whether to disable sandbox mode, default is false
  • proxy: Proxy server settings, supports socks5 proxy

Available tools

click

Click an element on the page to trigger navigation, UI changes, or actions within the page context.

screenshot

Capture the visible area or a specific region of the page and return or save the image.

pdf

Generate a PDF of the current page, including layout and printable content.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational