Skip to main content
Glama
polographer

mcp-flaresolverr

by polographer
README.md
# mcp-flaresolverr

A Node MCP (Model Context Protocol) server that exposes [FlareSolverr](https://github.com/FlareSolverr/FlareSolverr)'s anti-bot bypass capabilities — Cloudflare and DDoS-GUARD protection — to any MCP client.

## Installation

```sh
npx mcp-flaresolverr
```

Or install globally:

```sh
npm install -g mcp-flaresolverr
```

## Usage

Configure the server in your MCP client config and point it at your FlareSolverr instance:

```jsonc
{
  "mcp": {
    "servers": {
      "flaresolverr": {
        "command": "npx",
        "args": ["-y", "mcp-flaresolverr"],
        "env": {
          "FLARESOLVERR_URL": "http://localhost:8191"
        }
      }
    }
  }
}
```

## Tools

| Tool | Description |
|------|-------------|
| `flare_get` | HTTP GET through FlareSolverr — returns page content, cookies, headers |
| `flare_post` | HTTP POST through FlareSolverr — for form submissions and API calls |
| `flare_session_create` | Create a persistent browser session for faster subsequent requests |
| `flare_session_destroy` | Destroy a session and free resources |
| `flare_session_list` | List all active browser sessions |

## Configuration

| Environment Variable | Required | Description |
|---------------------|----------|-------------|
| `FLARESOLVERR_URL` | Yes | Base URL of your FlareSolverr instance (e.g. `http://localhost:8191`) |

## Development

```sh
npm install
npm run build
npm test
```

## License

MIT

TDQS

A3.7/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: two HTTP request methods (GET/POST) and three session management operations (list/create/destroy). No overlap or ambiguity; an agent can easily select the correct tool.

Naming Consistency4/5

All tools use snake_case with a consistent 'flare_' prefix, but the pattern is mixed: session tools include the resource noun 'session' (e.g., flare_session_create) while HTTP request tools omit it (e.g., flare_get). Minor deviation, still readable.

Tool Count5/5

Five tools is well-scoped for this domain: two core request methods and three session lifecycle operations. Each tool earns its place with no redundancy.

Completeness5/5

The surface covers the standard FlareSolverr API completely: GET/POST requests and session create/list/destroy. No obvious missing operations for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues