serpens-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAPIDAPI_KEY | No | Alternative to SERPENS_API_KEY. Provide this instead if you prefer. | |
| SERPENS_HOST | No | Override the API host. | serpens.p.rapidapi.com |
| SERPENS_API_KEY | No | Required. Your RapidAPI key for SERPens. Alternatively RAPIDAPI_KEY also works. | |
| SERPENS_TIMEOUT_MS | No | Client-side request 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| google_searchA | Search Google and get organic results — title, link, snippet, source, position, plus sitelinks, People Also Ask and related searches when Google renders them. Use for current facts, documentation lookups, and anything past the training cutoff. |
| google_ai_overviewA | Search Google and get its AI Overview — a synthesised answer with citations — alongside organic results. When Google renders no overview for the query, organic results still come back. Use when a summarised answer is more useful than a list of links. |
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
Both tools issue the same Google search, and google_ai_overview also returns organic results, so there is some overlap. However, google_search is clearly positioned as raw organic output while google_ai_overview targets the synthesized answer, making selection mostly unambiguous.
Both tools follow the same google_<output> pattern, with consistent snake_case and no stylistic mismatch. Even with only two tools, the naming convention makes each tool's return mode predictable.
Two tools is at the thin end of the scale, but the server is tightly focused on Google search output formats. It is borderline: enough to perform one useful task, but there is little room for broader SERP coverage.
For a server dedicated to Google search results, both the organic listing mode and the AI overview mode are present, so the core search workflow is covered. Missing advanced search types or filters are minor gaps that agents can work around rather than dead ends.