mcpField
F
flaresolverr

flaresolverr

github.com/magnus919Development15359 installsUpdated today
Repository

About flaresolverr

flaresolverr is a lightweight command-line skill that uses an already-running FlareSolverr instance when ordinary HTTP retrieval encounters a browser challenge. It provides health checks, GET and POST requests, and session operations, with JSON output.

Key features

  1. 01Runs health checks, GET, and POST
  2. 02Creates, lists, and destroys sessions
  3. 03Sets request timeouts
  4. 04Supports cookie continuity through sessions
  5. 05Returns response details as JSON

Use cases

  1. 01Checking a FlareSolverr instance
  2. 02Retrieving a page response through a browser challenge
  3. 03Making requests to sites that need cookie continuity

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/magnus919/agent-skills --skill flaresolverr

After installing, type/flaresolverrin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

README.md
evals/
evals.json
scripts/
flaresolverr
test-flaresolverr.sh

Details

From the project README

FlareSolverr

Quick Start

python3 scripts/flaresolverr --server http://localhost:8191 health

Use this skill when ordinary HTTP retrieval is blocked by a browser challenge. FlareSolverr must already be running; this skill does not bypass authentication or authorize access to restricted content.

When not to use

Use flaresolverr-cli when the task names that CLI, requires creating/listing/destroying named sessions, needs cookie-only responses or dry-run planning, or needs the full operational command surface. Keep this skill for the smaller one-off health, GET, or POST path.

Mutation Gate

The health command is read-only discovery. GET and POST send traffic to an external target, and POST may change target state.

Confirm the target, scope, and rollback path before acting. Read-only discovery may proceed without confirmation.

A POST or any request intended to change target state requires an explicit user directive. This skill does not authorize deletion, privilege changes, authentication bypass, or irreversible cleanup.

CLI

python3 flaresolverr/scripts/flaresolverr --server http://localhost:8191 health
python3 flaresolverr/scripts/flaresolverr --server http://localhost:8191 get https://example.com
python3 flaresolverr/scripts/flaresolverr session create
python3 flaresolverr/scripts/flaresolverr session list
python3 flaresolverr/scripts/flaresolverr session destroy SESSION_ID

Every command emits JSON. get and post use FlareSolverr's /v1 API and preserve the returned status, URL, headers, and response body. Use --timeout to bound a request and --session when a site needs cookie continuity.

Setup

Run FlareSolverr separately, commonly with Docker:

services:
  flaresolverr:
    image: ghcr.io/flaresolverr/flaresolverr:latest
    ports: ["8191:8191"]
    environment:
      LOG_LEVEL: info

Do not expose the service publicly. Prefer a pinned image tag in production and use the vendor's documentation for browser and platform compatibility.

Available Scripts

ScriptPurposeInvocation
scripts/flaresolverrMinimal JSON CLI for the FlareSolverr API: health, get, post, and session subcommands with --server and --timeout options. Run it for the one-off health check or challenge-solving GET/POST described above, and for short-lived session create/list/destroy when a site needs cookie continuity.python3 scripts/flaresolverr --server http://localhost:8191 get https://example.com
scripts/test-flaresolverr.shShell smoke test: verifies --help output and byte-compiles the CLI. Run it after modifying scripts/flaresolverr or when auditing the bundled script; CI runs it via scripts/check-skill-tests.py.sh scripts/test-flaresolverr.sh

Prerequisites

  • Python 3 with the standard library only; the CLI has no third-party dependencies.
  • A reachable FlareSolverr instance (commonly via Docker, per Setup above) — the CLI is a client and starts nothing itself.
  • Network access from the FlareSolverr instance to the target site; this skill does not bypass authentication or grant access to content you are not otherwise entitled to retrieve.

Limitations

  • The wrapper covers only the one-off health, get, post, and session paths; named-session lifecycle management, cookie-only returns, and dry-run planning belong to flaresolverr-cli (see When not to use).
  • Every command emits JSON and reports what FlareSolverr returned; it does not parse, extract, or rank page content for you.
  • Solving a browser challenge is not a guarantee: sites may still block, captcha, or rate-limit the underlying browser, and --timeout bounds only the request, not the target's behavior.

Comments

Markdown supported