Riddle

Wraps the Riddle API for Claude Code to take screenshots, automate browser tasks, and capture logs and HAR data.

javascript

0

GitHub Stars

javascript

Language

6 months ago

First Indexed

3 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": {
    "davisdiehl-riddle-mcp-server": {
      "command": "node",
      "args": [
        "/path/to/riddle-mcp-server/index.js"
      ],
      "env": {
        "RIDDLE_API_KEY": "rdc_live_your_key_here"
      }
    }
  }
}

You have a dedicated MCP server that wraps the Riddle API to integrate Claude Code workflows. It lets you take screenshots, run browser automation, and capture console logs plus network HAR data, all through simple MCP tool calls. This guide shows you how to install, configure, and use the server end to end.

How to use

Connect to the Riddle MCP server from your MCP client within Claude Code. You will configure a local (stdio) MCP server, start the server, and then use the provided tools to take screenshots, automate browser actions, and retrieve artifacts like console logs and HAR data.

How to install

Prerequisites you need before installation are Node.js and npm. Ensure both are available in your environment.

Step by step install flow:

Clone this server repository.
Install dependencies.
Configure Claude Code to load the MCP server using the following settings.

{
  "mcpServers": {
    "riddle": {
      "command": "node",
      "args": ["/path/to/riddle-mcp-server/index.js"],
      "env": {
        "RIDDLE_API_KEY": "rdc_live_your_key_here"
      }
    }
  }
}

Configuration details and usage notes

Launch the server after you have saved the MCP settings in Claude Code. The server runs locally as a stdio process, and Claude Code communicates with it over standard input/output.

Available tools and how to use them

The server exposes a set of tools you can call from your MCP client. You can take screenshots, run Playwright-based automation, and work with job-based or batch operations to collect artifacts.

Troubleshooting and notes

If you encounter connection or artifact issues, verify that the RIDDLE_API_KEY is set in the server environment and that the path to the index.js file is correct. Restart Claude Code after updating the MCP settings. If you see missing artifacts, check the console logs captured by the automation runs for errors and ensure the target URLs are reachable.

Available tools

riddle_screenshot

Take a screenshot of a given URL and return a base64-encoded PNG. Use a device preset or specify custom width and height for the viewport.

riddle_batch_screenshot

Capture screenshots for multiple URLs in one call using a single device preset.

riddle_automate

Execute a Playwright script, wait for completion, and collect artifacts including screenshots, console logs, and a network HAR summary.

riddle_run_script

Run a Playwright script asynchronously and obtain a job_id to check progress later.

riddle_get_job

Retrieve the status and artifacts for a previously started async job.

riddle_click_and_screenshot

Load a URL, click a selector, and take a screenshot in one simple call.