Thunder
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OLLAMA_HOST | No | Ollama host used for offline pairing with a local model. Auto-detected along with OLLAMA_MODEL. | |
| OLLAMA_MODEL | No | Ollama model name used for offline pairing with a local model. Auto-detected along with OLLAMA_HOST. | |
| STEWMIND_LOCAL | No | Set to 1 to enable auto-detection of a local stewmind model. | |
| CAPSOLVER_API_KEY | No | Bring-your-own CapSolver API key for solving CAPTCHAs on your own accounts. | |
| TWOCAPTCHA_API_KEY | No | Bring-your-own 2Captcha API key for solving CAPTCHAs on your own accounts. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| thunder_openC | Open a URL in Thunder's human-shaped browser body. |
| thunder_readB | Read the current page: title, url, text, clickable elements. |
| thunder_clickC | Click like a human (bezier mouse path + human timing). |
| thunder_typeB | Type like a human (inter-key delays, rare typos, pauses). |
| thunder_scrollC | Scroll with human easing and reading pauses. |
| thunder_lookA | Take a screenshot of the current page; returns the file path. |
| thunder_ghostB | Fetch a URL with a real browser TLS fingerprint (curl_cffi). |
| thunder_captchaB | Detect CAPTCHA challenges on the current page. |
| thunder_thinkC | Ask stewmind-1.7b for the next action toward a goal. |
| thunder_restB | Close the body. Cookies/fingerprint persist for next time. |
| thunder_searchB | Search the web (Google, Bing or DuckDuckGo — auto falls back ddg->bing->google) with a browser-true TLS handshake. The result names the engine used. |
| thunder_feelC | Probe a URL's bot posture: plain request vs thunder ghost (TLS-true) request. |
| thunder_identityB | Export the live fingerprint, or wear one from a fingerprint JSON file (Skin.imitate). |
| thunder_human_readC | Read the current page like a human: burst scroll, reading pauses, idle hand drift. |
| thunder_challengeB | Detect and counter any CAPTCHA/challenge on the current page (Turnstile/reCAPTCHA/hCaptcha/Amazon/CF interstitial) — keyless. |
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 15 tools
Most tools are distinct, but several pairs overlap: thunder_read vs thunder_human_read, thunder_captcha vs thunder_challenge, and thunder_ghost/thunder_feel/thunder_search all involve browser-TLS fetching. thunder_rest is especially unclear as a name for closing the browser body.
The thunder_ prefix is consistent, but suffixes mix verbs (open, read, click) with nouns (captcha, identity, challenge, ghost) and compounds (human_read). Some names like thunder_rest and thunder_feel are cryptic about what they actually do.
15 tools is reasonable for a stealth browser automation server covering navigation, interaction, fingerprinting, CAPTCHA handling, search, and planning. There is slight redundancy in the CAPTCHA and page-reading tools, but the count is not excessive.
Core browser lifecycle is covered: open, read, click, type, scroll, screenshot, and close. It also adds fingerprinting, search, CAPTCHA handling, and a reasoning helper; minor gaps like tab management, navigation history, or explicit waits are workaroundable.