Google News MCP Server

Created By
ChanMeng666a year ago
【Star-crossed coders unite!⭐️】Model Context Protocol (MCP) server implementation providing Google News search capabilities via SerpAPI, with automatic news categorization and multi-language support.
Overview

What is Google News MCP Server?

The Google News MCP Server is an implementation of the Model Context Protocol (MCP) that enables users to search for news via Google's news API, offering features like automatic news categorization and multi-language support.

How to use Google News MCP Server?

To use the Google News MCP Server, first obtain a SERP API key from the SERP API website, then install the necessary dependencies, configure your environment, build the server, and start it to begin performing news searches.

Key features of Google News MCP Server?

  • Flexible search options including topic and publication filtering.
  • Supports multiple languages and regions.
  • Automatically categorizes news into topics such as AI & Technology and Business.
  • Handles various news result types including headlines and related topics.
  • Robust error handling for seamless user experience.

Use cases of Google News MCP Server?

  1. Searching for the latest news articles in specified categories.
  2. Aggregating news from multiple languages for broader coverage.
  3. Deploying on a local server for custom news solutions.

FAQ from Google News MCP Server?

  • What is required to get started?

You need a SERP API key, Node.js, and the project dependencies installed.

  • Can I use the server for multiple languages?

Yes, the server supports multiple languages as specified in your configuration.

  • Is there any API usage limit?

Yes, the free tier allows 100 searches per month, with additional paid plans available.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ChanMeng666
Star
46
Language
JavaScript
License
MIT 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)

a day ago