web-scrapper-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTPS_PROXY | No | Optional proxy URL for corporate proxy (e.g., http://proxy:8080) | |
| SCRAPER_OUTPUT_DIR | No | Directory where screenshots are saved | output |
| SCRAPER_TIMEOUT_MS | No | Page load timeout in milliseconds | 30000 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scrape_pageA | Scrape any SPA or JS-rendered webpage and return its content. Args: url: The page URL to scrape. wait_for: Playwright wait state — 'networkidle' | 'load' | 'domcontentloaded'. selector: Optional CSS selector to wait for before returning content. mode: Output format — 'markdown' | 'html' | 'text'. wait_ms: Extra settle delay in milliseconds after the page loads. Returns: {content, page_title, url, word_count, mode} |
| extract_api_endpointsA | Extract structured API endpoint data from an API documentation site. Automatically detects the site type (swagger, redoc, stoplight, fmp, generic). Override detection by passing site_type explicitly. Args: url: URL of the API documentation page. site_type: Force a specific extractor — 'swagger' | 'redoc' | 'stoplight' | 'fmp' | 'generic'. Returns: { endpoints: [{method, path, operation_id, summary, description, tags, parameters}], count: int, site_type: str, url: str, } |
| screenshot_pageA | Take a full-page screenshot of a URL for visual debugging. Returns the file path and the PNG encoded as base64 so the agent can display it inline. Args: url: URL to screenshot. full_page: Capture the full scrollable page (default True). Returns: {saved_path: str, base64: str} |
| scrape_and_seedA | Scrape API documentation and seed a finanal-style SQLite database directly. The target database must have an 'endpoints' table with columns: path, method, operation_id, summary, description, tags, parameters, source Args: url: URL of the API documentation page. db_path: Absolute path to the SQLite database file. source_name: Label for the 'source' column (e.g. 'fmp', 'tapetide'). site_type: Optional site type override for the extractor. Returns: {seeded: int, skipped: int, source: str, db_path: str} |
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: extracting API endpoints, seeding a database, scraping general web pages, and taking screenshots. No two tools overlap in function.
All names use snake_case, but the verb patterns are inconsistent: 'extract_api_endpoints' and 'scrape_page' follow verb_noun, while 'scrape_and_seed' uses 'and', and 'screenshot_page' is a noun_verb combination.
4 tools is well-scoped for a web scraping server. Each tool covers a core functionality without unnecessary redundancy or missing essentials.
The server covers core scraping needs (API extraction, general scraping, screenshot, database seeding). Minor gaps like multi-page crawling or link extraction are absent but not critical for the stated purpose.