Serper

Created By
garymengcoma year ago
Overview

what is Serper?

Serper is a Model Context Protocol (MCP) server that provides Google Search capabilities via Serper, enabling large language models (LLMs) to retrieve search result information from Google.

how to use Serper?

To use Serper, you can set it up in your MCP client by configuring it with your Serper API key and following the installation instructions for either uv or pip.

key features of Serper?

  • Integration with Google Search for LLMs
  • Customizable search parameters (location, language, time period)
  • Supports multiple installation methods (uv, pip)

use cases of Serper?

  1. Enhancing LLMs with real-time search capabilities.
  2. Enabling chatbots to provide up-to-date information.
  3. Assisting in research by fetching relevant data from Google.

FAQ from Serper?

  • What is the purpose of Serper?

Serper allows LLMs to access Google Search results, enhancing their ability to provide accurate and current information.

  • How do I install Serper?

You can install Serper using uv or pip, following the provided configuration instructions.

  • Is there a license for Serper?

Yes, Serper is licensed under the MIT License, allowing free use, modification, and distribution.

Server Config

{
  "mcpServers": {
    "serper": {
      "command": "uvx",
      "args": [
        "serper-mcp-server"
      ],
      "env": {
        "SERPER_API_KEY": "<Your Serper API key>"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
garymengcom
Star
-
Language
-
License
-

Recommend Servers

View All
Crevio

a day ago
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)

19 hours ago