serpapi/serpapi-mcp

A Model Context Protocol (MCP) server implementation that integrates with SerpApi for comprehensive search engine results and data extraction.
Features
- **Multi-Engine Search**: Google, Bing, Yahoo, DuckDuckGo, YouTube, eBay, and more
- **Engine Resources**: Per-engine parameter schemas available via MCP resources (see Search Tool)
- **Real-time Weather Data**: Location-based weather with forecasts via search queries
- **Stock Market Data**: Company financials and market data through search integration
- **Dynamic Result Processing**: Automatically detects and formats different result types
- **Flexible Response Modes**: Complete or compact JSON responses
- **JSON Responses (default)**: Structured JSON output with complete or compact modes
- **Markdown Responses**: Cut token usage by 50% on average and by more than 90% for APIs with complex nested JSON.
- **Interactive UI (MCP Apps)**: Opt-in search_table and search_dashboard tools that render results as an interactive UI in supporting hosts
- **Claude Desktop Extension**: One-click local install from an MCP Bundle (.mcpb), see below
Quick start
SerpApi MCP Server is available as a hosted service at mcp.serpapi.com. In order to connect to it, you need to provide an API key. You can find your API key on your SerpApi dashboard.
You can configure Claude Desktop to use the hosted server:
You can also add the hosted server to these MCP clients:
**OpenClaw**
**Claude Code**
**Hermes**
**Codex** (reads the key from SERPAPI_API_KEY in your shell)
Self-hosting
Configure Claude Desktop:
Get your API key: serpapi.com/manage-api-key
Claude Desktop Extension (MCP bundle)
For a local, one-click install, download the .mcpb bundle from the latest release (or build it as below) and open it with Claude Desktop (or drop it onto **Settings → Extensions**). Claude Desktop asks for your SerpApi API key during install, stores it as a sensitive setting, and runs the server locally over stdio. The bundle uses the MCPB uv runtime: it ships only the source, pyproject.toml and uv.lock, and Claude Desktop provisions Python and the locked dependencies with uv at install time, so nothing is vendored and one bundle works on macOS, Windows and Linux.
Everything bundle-related lives in mcpb/, plus .mcpbignore at the project root. The build regenerates the engine schemas from the SerpApi Playground (--no-rebuild-engines bundles engines/ from the working tree instead), validates mcpb/manifest.json, packs the git-tracked files minus .mcpbignore with the manifest at the bundle root, then installs it into a temp dir and starts it over stdio to make sure it works (--no-smoke skips that last step). The bundle is only built at release time: pushing a v tag runs the release workflow, which runs the test suite and then deploys the hosted server, publishes the MCP Registry entry, and builds the bundle and attaches it to the GitHub release. Pull requests run the manifest and stdio entry point tests in tests/test_mcpb.py but do not pack a bundle.
The same stdio entry point works with any local MCP host that launches servers as a subprocess:
Authentication
Two methods are supported:
- **Header-based**: Authorization: Bearer YOUR_API_KEY (recommended: the key stays out of URLs and logs)
- **Path-based**: /YOUR_API_KEY/mcp, for clients that cannot set headers
**Examples:**
No key is needed to connect, list tools or read resources. search and the App tools need one and return an error without it.
Search tool
The MCP server has one main search tool that supports all SerpApi engines and result types. You can find all available parameters on the SerpApi API reference.
Engine parameter schemas are also exposed as MCP resources: serpapi://engines (index) and serpapi://engines/ .