mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | API key for Anthropic (required for chatbot) | |
| FIRECRAWL_API_KEY | Yes | API key for Firecrawl (required for scraping) |
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_websitesC | Scrape multiple websites using Firecrawl and store their content. Args: websites: Dictionary of provider_name -> URL mappings formats: List of formats to scrape ['markdown', 'html'] (default: both) api_key: Firecrawl API key (if None, expects environment variable) Returns: List of provider names for successfully scraped websites |
| extract_scraped_infoB | Extract information about a scraped website. Args: identifier: The provider name, full URL, or domain to look for Returns: Formatted JSON string with the scraped information |
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 2 tools
The two tools have clearly distinct purposes: one scrapes multiple websites and stores content, the other extracts specific information from a previously scraped website. No overlap in functionality.
Both tool names follow a consistent verb_noun pattern using snake_case: scrape_websites and extract_scraped_info. The naming is predictable and clear.
With only 2 tools, the server is minimal but adequately covers the core workflow of scraping and extracting. It could benefit from additional tools for management, but the count is not inappropriate for the stated purpose.
The server covers the primary operations of scraping and extraction, but lacks tools for listing, updating, or deleting scraped data, which could limit agent workflows. Some notable gaps exist.