The Web MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRO_MODE | No | Set to 'true' to enable 60+ Pro tools including browser automation and structured data extractors | false |
| API_TOKEN | Yes | Your Bright Data API token for authentication | |
| RATE_LIMIT | No | Custom rate limit configuration, e.g., '100/1h' | |
| BROWSER_ZONE | No | Custom Scraping Browser zone name | |
| WEB_UNLOCKER_ZONE | No | Custom Web Unlocker zone name |
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 | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_engineC | Scrape search results from Google, Bing or Yandex. Returns SERP results in markdown (URL, title, description) |
| scrape_as_markdownA | Scrape a single webpage URL with advanced options for content extraction and get back the results in MarkDown language. This tool can unlock any webpage even if it uses bot detection or CAPTCHA. |
| search_engine_batchC | Run multiple search queries simultaneously. Returns JSON for Google, Markdown for Bing/Yandex. |
| scrape_batchB | Scrape multiple webpages URLs with advanced options for content extraction and get back the results in MarkDown language. This tool can unlock any webpage even if it uses bot detection or CAPTCHA. |
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 4 tools
Each tool has a clearly distinct purpose: scrape_as_markdown handles single webpage scraping, scrape_batch handles multiple webpages, search_engine scrapes single search queries, and search_engine_batch handles multiple search queries. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent snake_case pattern with clear verb_noun structures: scrape_as_markdown, scrape_batch, search_engine, and search_engine_batch. The naming is predictable and aligns well with the actions each tool performs.
With 4 tools, the server is well-scoped for web scraping and search functionality. Each tool earns its place by covering distinct aspects of the domain: single and batch operations for both webpage scraping and search engine queries, avoiding bloat while providing essential coverage.
The tool set covers core web scraping and search operations effectively, including single and batch modes. A minor gap exists in lacking tools for more advanced interactions like form submission or dynamic content handling, but the provided tools support key workflows without dead ends.