← Tool directory
TOOL PROFILE

SerpApi MCP Server

Compare the same Google search across two locations and preserve result URLs and request settings in a market audit.

Open source

Community support

Upvotes come from SearchEngineAnswer members. GitHub stars and reader reviews are counted separately.

Claim this tool if you maintain it.

Best for
MCP servers
Setup required
Use an MCP client with Streamable HTTP and a SerpApi account key. The hosted server accepts an Authorization header and works with Codex.
Costs to check
MIT-licensed MCP server. Search calls consume the account's SerpApi allowance and may incur charges. Check the plan and request budget before scheduling batches.
License in catalog
MIT

GitHub repository

GitHub stars
187
Forks
45
Last push
2026-11-20
Primary language
Python

GitHub snapshot from . Stars count GitHub bookmarks. Reader ratings appear separately below.

How to install SerpApi MCP Server

  1. Create an API key in the SerpApi account you intend to use and place it in the SERPAPI_API_KEY environment variable used by Codex. Leave the key out of prompts and shared configuration samples.
    codex mcp add serpapi --url https://mcp.serpapi.com/mcp --bearer-token-env-var SERPAPI_API_KEY
  2. Register the hosted endpoint with the command below. Restart the client if needed and confirm it can list the search tool and read the google engine resource.

First tutorial for SerpApi MCP Server

  1. Request one Google search for coffee shops using Austin, Texas, United States as the location. Return the first three organic URLs and the location reported in the response.
    {
      "name": "search",
      "arguments": {
        "params": {
          "engine": "google",
          "q": "coffee shops",
          "location": "Austin, Texas, United States",
          "gl": "us",
          "hl": "en",
          "device": "desktop"
        },
        "mode": "complete"
      }
    }
  2. Run the same request for Seattle, Washington, United States. Keep the language, country, device and request time window as close as possible.
  3. Check whether the reported locations differ as intended. Mark a missing organic section as unavailable and preserve the raw response before summarizing which URLs differed.

GitHub v2.3.0 was released November 12, 2026. The two-market exercise is a proposed check. It uses illustrative locations and requires two authorized search requests.

Official installation and usage documentation ↗

Where SerpApi MCP Server fits

Choose SerpApi MCP when an agent needs a structured search snapshot with its query parameters and source URLs for later review.

When to choose another tool
Use a manual browser search to confirm how a result page looks in one environment. Use Search Console for clicks and impressions actually attributed to your own property.
First evaluation
Use one stable local-intent query and two locations supported by the Google engine. Keep the language, country and device equal and retain the complete responses.
How to interpret the result
Compare result features and destination URLs by market. A sampled rank is tied to the collection settings and time. Keep retrieved results distinct from query volumes and customer behavior.

Reviews and discussion

Reader reviews

Be the first to share your experience with this tool.

Discussion

Ask a question or share a setup tip.

Write a review or join the discussion

Reviews should describe your own experience. All submissions are moderated.

Flag an outdated detail

Include the field that needs updating and a source link. Copy your draft, then use the corrections policy to contact the editorial team.