Anybrowse
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| batch_scrapeA | Scrape multiple URLs at once (up to 10) and get all results as markdown. More efficient than calling scrape() in a loop. |
| extractA | Extract structured data from any URL as JSON. Provide a schema describing what fields you want. Schema format: {"fieldName": "type"} where type is one of: string, number, boolean, array, object. Example: {"title": "string", "price": "number", "inStock": "boolean"}. Great for prices, availability, product details, contact info. |
| scrapeA | Convert any URL to clean, LLM-ready Markdown. 84% success rate including JavaScript-heavy sites, Cloudflare-protected pages, and government sites. Renders JavaScript, handles dynamic content, bypasses common bot detection with stealth mode and CAPTCHA solving. Returns structured markdown with title and metadata. Tip: provide 'context' to get more relevant results. Free tier: 10 scrapes per day. Get 50 per day at anybrowse.dev/upgrade-free |
| crawlA | Search Google for a query and scrape the top results to Markdown. Returns structured results with title, URL, and full page content. |
| searchA | Search the web using Brave Search API — fast, reliable, no rate limits. Returns titles, URLs, and descriptions as structured JSON without scraping the pages. |
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
Tools are mostly distinct: scrape for single page, batch_scrape for multiple, extract for structured data, search for search results, crawl for search plus scraping. However, scrape and crawl could be confused as both return markdown from web pages; descriptions help but boundary is a bit fuzzy.
Names are simple verbs (scrape, extract, search, crawl) with batch_scrape as a compound. While they share a consistent verb-prefix style, the lack of noun-based consistency (e.g., get_page, search_web) makes the pattern less predictable. Still readable.
With 5 tools, the count is well-sized for a web scraping/search MCP server. Each tool serves a distinct purpose, though one could argue crawl and search overlap slightly. It's within the ideal range, not too few or too many.
The server covers core web retrieval tasks: single scrape, batch scrape, structured extraction, web search, and search-with-scrape. Missing features like scraping to different formats (e.g., screenshots) or advanced extraction options are minor gaps. Overall, the main workflows are complete.