mcp-flaresolverr
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLARESOLVERR_URL | Yes | Base URL of your FlareSolverr instance (e.g. `http://localhost:8191`) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| flare_getA | Make an HTTP GET request through FlareSolverr to bypass Cloudflare/DDoS protection. Returns the page content, cookies, and headers after the challenge is solved. |
| flare_postB | Make an HTTP POST request through FlareSolverr to bypass Cloudflare/DDoS protection. Useful for submitting forms or API calls behind protection. |
| flare_session_createB | Create a persistent browser session. This speeds up subsequent requests since the browser doesn't need to launch a new instance for every request. |
| flare_session_destroyA | Destroy a browser session and free up resources. Always close sessions when done. |
| flare_session_listA | List all active browser sessions. Useful for debugging and monitoring. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
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.
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.
The surface covers the standard FlareSolverr API completely: GET/POST requests and session create/list/destroy. No obvious missing operations for the stated purpose.