Skip to main content
Glama
Sign In
SerpApi MCP Server

SerpApi MCP Server

by serpapi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SERPAPI_API_KEYYesYour SerpApi API key

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
completions
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_dashboardA

Interactive dashboard variant of search: returns summary metrics, a source breakdown chart, and a results table with a click-to-expand detail panel, all rendered in the conversation. Same params as search. Use for a richer visual overview of a query's results. Automatically selects an engine-specific dashboard when available (e.g. google_flights gets price intelligence charting).

search_tableA

Interactive UI variant of search: returns organic results as a sortable, searchable table rendered in the conversation. Same params as search. Use when the host supports MCP Apps and the user wants to browse results visually rather than read JSON.

searchA

Universal search tool supporting all SerpApi engines and result types.

When to use:
    - Any query needing live, structured SERP data: web results, news, product listings, job postings, local businesses, flight/hotel prices, video results, images, stock/weather cards, knowledge graph entities.

Engine discovery via MCP resources:
    - serpapi://engines lists all engines supported by this tool.
    - serpapi://engines/<engine> provides engine-specific parameters and supported options.
    - Example: serpapi://engines/google_news

Input schema:
    params: JSON object containing SerpApi engine parameters.
        Common parameters:
            - q: Search query. Required for most engines.
            - engine: SerpApi engine name. Defaults to "google_light".
            - location: Optional geographic location for localized results.
            - output: Optional response format. Omit for JSON (default), or set to "md" for Markdown.

        Engine-specific parameters are available via MCP resources:
            - serpapi://engines lists all supported engines.
            - serpapi://engines/<engine> provides parameters and options for one engine.

    mode: Response mode. Defaults to "complete".
        - "complete": Return the full SerpApi response.
        - "compact": Remove metadata fields from JSON responses. Markdown is returned unchanged.

Output schema:
    structuredContent.result contains the response string: serialized JSON or unchanged Markdown.
    The same string is included in text content. Tool failures preserve this wrapper and set isError to true.

Guided search:
    Searches can request missing engine parameters from supporting clients using the engine catalog and engine-specific rules.
    Flights collect airports and dates, hotels collect the destination and stay dates, and directions collect missing endpoints.
    Other clients receive a missing-parameter error. Cancellation does not run a search.

Examples:
    Weather: {"params": {"q": "weather in London", "engine": "google"}, "mode": "complete"}
    Stock: {"params": {"q": "AAPL stock", "engine": "google"}, "mode": "complete"}
    General: {"params": {"q": "coffee shops", "engine": "google_light", "location": "Austin, TX"}, "mode": "complete"}
    Compact: {"params": {"q": "news"}, "mode": "compact"}
    Markdown: {"params": {"q": "news", "output": "md"}}

Supported engines include (not limited to):
    - google
    - google_light
    - google_flights
    - google_hotels
    - google_images
    - google_news
    - google_local
    - google_shopping
    - google_jobs
    - bing
    - yahoo
    - duckduckgo
    - youtube_search
    - baidu
    - ebay

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
serpapi-engines-indexIndex of available SerpApi engine identifiers.
Prefab Renderer (search_dashboard)
Prefab Renderer (search_table)
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored across 3 tools

Disambiguation4/5

The three tools share the same underlying search parameters, but their output modes are clearly differentiated: raw structured results, a dashboard summary, and a sortable table. There is some potential confusion because all three perform the same query, but the presentation-focused descriptions make selection reasonably clear.

Naming Consistency4/5

All names use snake_case and share a predictable `search_*` prefix, with suffixes describing the output variant. The base `search` tool omits a suffix, which is a minor deviation but still readable and consistent overall.

Tool Count5/5

Three tools is well-scoped for a universal search server: one core search tool and two optional visual presentation variants. Each tool has a clear role, and the surface avoids unnecessary bloat.

Completeness4/5

The core search lifecycle is covered across all supported SerpApi engines, with engine discovery handled through MCP resources rather than tools. Minor gaps exist around account/usage inspection or explicit engine-listing tools, but agents can work around them via resources and search parameters.

Maintenance

ActivityActive
ResponsivenessSyncing

Resources