WebScraper MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP server port (default: 3000, only for HTTP transport) | |
| TRANSPORT | No | Transport type ('stdio' or 'http', default: 'stdio') |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scrape_pageB | Scrape a web page and convert it to Markdown format. Returns the page content, metadata, and extracted information. |
| extract_linksA | Extract all links from a web page. Returns a list of links with their text, URLs, and metadata. |
| extract_imagesA | Extract all images from a web page. Returns a list of images with their URLs, alt text, and metadata. |
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 3 tools
Each tool has a distinct purpose: scrape_page retrieves page content, extract_links gets hyperlinks, and extract_images gets images. There is clear separation of concerns with no overlapping functionality.
All tool names follow a consistent verb_noun pattern in snake_case (scrape_page, extract_links, extract_images). While 'scrape' and 'extract' differ, they are appropriate verbs for their respective actions, and the pattern is uniform.
Three tools is well-scoped for a focused web scraping server. Each tool covers a core aspect of scraping without redundancy, fitting comfortably within the ideal 3-15 range.
The set covers fundamental scraping needs: content, links, and images. It could be extended with custom selector support or structured data extraction, but the current surface handles basic workflows without dead ends.