SerpApi Mcp

Created By
serpapi6 months ago
SerpApi MCP Server for Google and other search engine results
Overview

What is SerpApi MCP?

SerpApi MCP is a Model Context Protocol server that integrates with SerpApi to provide comprehensive search engine results and data extraction from various platforms.

How to use SerpApi MCP?

To use SerpApi MCP, you can either access the hosted service at mcp.serpapi.com with your API key or self-host the server by cloning the repository and running it locally.

Key features of SerpApi MCP?

  • Multi-engine search capabilities including Google, Bing, Yahoo, and more.
  • Real-time weather data retrieval based on search queries.
  • Access to stock market data and company financials.
  • Dynamic result processing that formats different result types automatically.
  • Flexible response modes for JSON output.

Use cases of SerpApi MCP?

  1. Extracting search results from multiple engines for research purposes.
  2. Retrieving real-time weather information for specific locations.
  3. Accessing stock market data for financial analysis.
  4. Automating data extraction for various applications.

FAQ from SerpApi MCP?

  • Can I use SerpApi MCP for all search engines?

Yes! SerpApi MCP supports multiple search engines including Google, Bing, and more.

  • Is there a cost associated with using SerpApi MCP?

SerpApi MCP requires an API key, and usage may depend on your SerpApi plan.

  • How do I troubleshoot API key issues?

Ensure your API key is included in the URL path or header, and verify its validity on the SerpApi dashboard.

Server Config

{
  "mcpServers": {
    "serpapi": {
      "url": "https://mcp.serpapi.com/YOUR_SERPAPI_API_KEY/mcp"
    }
  }
}
Project Info
Created At
6 months ago
Updated At
6 months ago
Author Name
serpapi
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 hours ago
Gpt Scrambler

2 days ago