solocrawl
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SOLOCRAWL_LOG_FILE | No | Optional log file path (also logs to stderr) | |
| SOLOCRAWL_LOG_LEVEL | No | Log level: DEBUG, INFO, WARNING, ERROR | |
| SOLOCRAWL_PROXY_LIST | No | Comma-separated proxy URLs | |
| SOLOCRAWL_PROXY_MODE | No | Proxy mode: list (rotate a pool) or endpoint (single rotating endpoint) | |
| SOLOCRAWL_USER_AGENT | No | Override HTTP User-Agent for API requests | |
| SOLOCRAWL_MAX_RETRIES | No | Retries on network errors / rate limits | |
| SOLOCRAWL_SEARXNG_URL | No | Base URL of a self-hosted SearXNG instance (enables the searxng provider) | |
| SOLOCRAWL_PROXY_ENABLED | No | Enable optional proxy layer | |
| SOLOCRAWL_PROXY_ENDPOINT | No | Single rotating proxy endpoint | |
| SOLOCRAWL_PROXY_PASSWORD | No | Proxy auth password | |
| SOLOCRAWL_PROXY_USERNAME | No | Proxy auth username | |
| SOLOCRAWL_RESPECT_ROBOTS | No | Honour robots.txt on scrape (fail-open); set false to skip | |
| SOLOCRAWL_BROWSER_ALLOWED | No | Allow Playwright fallback when installed | |
| SOLOCRAWL_MAX_CONCURRENCY | No | Global fetch concurrency limit | |
| SOLOCRAWL_TIMEOUT_SECONDS | No | Per-request timeout in seconds | |
| SOLOCRAWL_ENABLE_PROVIDERS | No | Comma-separated opt-in provider names | |
| SOLOCRAWL_PER_DOMAIN_LIMIT | No | Per-domain concurrency limit | |
| SOLOCRAWL_CACHE_TTL_SECONDS | No | In-memory fetch cache TTL in seconds (0 = disabled) | |
| SOLOCRAWL_MAX_RESPONSE_BYTES | No | Cap on fetched response body size (10 MiB) | |
| SOLOCRAWL_ALLOW_INTERNAL_URLS | No | Allow scraping localhost/private IPs (dev only) |
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
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchB | Search the web across SoloCrawl's configured providers and return unified results. |
| scrapeA | Fetch a URL and return the main page content as markdown suitable for LLM context. |
| researchB | Search the web, scrape the top results, and return an aggregated cited report. |
| package_versionB | Look up the latest or constraint-satisfying version of a package from a registry. |
| list_providersB | List the registered search and package providers (default vs. opt-in). |
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
web_search, scrape, and research have overlapping search/scrape functionality, but their descriptions clearly differentiate outputs (raw results vs. single-page markdown vs. aggregated cited report). package_version and list_providers are unambiguously distinct, so only minor misselection risk exists.
All names use lowercase snake_case for multiword terms, but grammatical patterns vary: scrape/research are bare verbs, package_version is noun_noun, web_search is noun_verb, and list_providers is verb_noun. The mix is readable but lacks a predictable convention.
Five tools is well-scoped for a web research and crawling server. Each tool covers a distinct operation (search, scrape, aggregate research, package lookup, provider listing) without redundancy or bloat.
Core search, scrape, and research workflows are covered, and package lookup is a useful addition. However, a server named solocrawl lacks a multi-page crawl or batch scrape tool, and provider configuration is absent, leaving minor gaps.