SERPJET MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERPJET_API_KEY | Yes | Your API key from serpjet.io | |
| SERPJET_API_BASE | No | Override API base URL (default https://api.serpjet.io) | https://api.serpjet.io |
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 |
|---|---|
| google_searchA | Search Google and get structured JSON results via SERPJET (serpjet.io). Supports 10 result types: web search, images, videos, news, shopping (with prices), maps, places, scholar, patents, and autocomplete. Free tier: 1,000 searches/month, recurring. Each successful call uses 1 credit. |
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 1 tool
With only a single tool, there is no risk of confusing different tools. The tool's purpose is clearly defined.
There is only one tool, so naming consistency is moot. The name 'google_search' is clear and follows a common verb_noun pattern.
The server has a single tool, which is slightly thin for a search service that supports multiple result types. However, the tool is comprehensive enough to cover many use cases, making it reasonable.
The tool covers 10 different search result types (web, images, videos, news, shopping, maps, places, scholar, patents, autocomplete), leaving no obvious gaps for a search tool.