MCP News API Server

Created By
matteoantocia year ago
An MCP server exposing News API endpoints for searching and retrieving news articles. Provides reliable, easy-to-use tools for integrating news data into applications and workflows, with robust error handling and secure API key management.
Overview

What is MCP News API Server?

MCP News API Server is a Model Context Protocol (MCP) server that exposes endpoints from the News API to search for and retrieve news articles, allowing programmatic access to news data.

How to use MCP News API Server?

To use the MCP News API Server, clone the repository, install dependencies, set your News API key in the environment, and run the server using Node.js.

Key features of MCP News API Server?

  • Exposes News API endpoints for searching and retrieving news articles.
  • Robust error handling and secure API key management.
  • Supports multiple input parameters for customized news searches.

Use cases of MCP News API Server?

  1. Integrating news data into applications and workflows.
  2. Building news aggregation tools.
  3. Creating custom news feeds based on user preferences.

FAQ from MCP News API Server?

  • How do I get a News API key?

You can obtain a News API key by signing up at https://newsapi.org.

  • What programming language is used?

The server is built using TypeScript.

  • Is there any error handling?

Yes, the server provides meaningful error messages based on the News API response.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
matteoantoci
Star
0
Language
TypeScript
License
View 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)

2 hours ago