serper-search-scrape-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERPER_API_KEY | Yes | Your Serper API key for web search and content extraction |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| google_searchC | Tool to perform web searches via Serper API and retrieve rich results. It is able to retrieve organic search results, people also ask, related searches, and knowledge graph. |
| scrapeC | Tool to scrape a webpage and retrieve the text and, optionally, the markdown content. It will retrieve also the JSON-LD metadata and the head metadata. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| research-topic | Guide comprehensive research on a topic with structured results |
| compare-sources | Compare information from multiple sources on a topic |
| fact-check | Verify a claim across multiple authoritative sources |
| technical-search | Focused technical and programming search |
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: google_search is for performing web searches and retrieving search results, while scrape is for extracting content from a specific webpage. There is no overlap in functionality, making it easy for an agent to choose the right tool for each task.
Both tools follow a consistent naming pattern using snake_case with descriptive, action-oriented names (google_search and scrape). The naming is straightforward and predictable, with no deviations or mixed conventions.
With only 2 tools, the server feels thin for a search-and-scrape domain, as it might lack additional utilities like batch processing, advanced filtering, or result summarization. However, the core functions are covered, making it borderline but functional.
The tools cover the essential workflows for search and scraping: performing searches and extracting webpage content. Minor gaps exist, such as no tool for managing search history or handling pagination, but agents can work around these with the provided tools.