Serper Search and 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 used to perform web searches and webpage 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 | {} |
| prompts | {} |
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 performs web searches and retrieves search results, while scrape extracts content from a specific webpage. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the task.
Both tools follow a consistent snake_case naming convention with descriptive, action-oriented names (google_search and scrape). The naming pattern is uniform and predictable, enhancing readability and usability.
With only 2 tools, the server feels thin for a search and scrape domain, potentially lacking operations like advanced filtering, batch processing, or handling specific content types. While the tools cover core functionalities, the count is borderline minimal for the apparent scope.
The server provides basic search and scrape capabilities, but there are notable gaps such as no tools for managing search history, handling pagination in results, or extracting structured data beyond text/metadata. This may limit agents in complex workflows, though core operations are present.