Serper Search and Scrape MCP Server

Created By
marcopesania year ago
Serper MCP Server supporting search and webpage scraping
Overview

what is Serper Search and Scrape MCP Server?

Serper Search and Scrape MCP Server is a TypeScript-based server that provides web search and webpage scraping capabilities using the Serper API, integrating with Claude Desktop for enhanced content extraction.

how to use Serper Search and Scrape MCP Server?

To use the server, install the dependencies, build the server, and configure it with your Serper API key. You can then run it alongside Claude Desktop for web search and scraping functionalities.

key features of Serper Search and Scrape MCP Server?

  • Web Search: Perform searches via the Serper API with rich results including organic results and knowledge graphs.
  • Web Scraping: Extract content from web pages, preserving document structure and metadata.
  • Environment Configuration: Easy setup with environment variables and configuration files.

use cases of Serper Search and Scrape MCP Server?

  1. Conducting automated web searches for data collection.
  2. Scraping content from websites for research or analysis.
  3. Integrating with applications that require real-time web data.

FAQ from Serper Search and Scrape MCP Server?

  • What are the requirements to run the server?

You need Node.js version 18 or higher and a valid Serper API key.

  • Can I use this server on different operating systems?

Yes! The server can be configured on both MacOS and Windows.

  • How do I debug the server?

You can use the MCP Inspector for debugging, which provides a URL for browser-based debugging tools.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
marcopesani
Star
2
Language
TypeScript
License
MIT license
Tags

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)

a day ago