NewzAI MCP Server

What NewzAI MCP Server does

NewzAI MCP Server MCP server connects MCP-compatible AI clients to the NewzAI news retrieval layer. It returns current headlines and detailed articles rather than requiring the client to scrape pages or parse RSS feeds. Results can be scoped by region, language, topic, article count, and—in custom searches—recency.

The supported regions are India, the United States, the United Kingdom, Japan, Australia, Canada, and Germany. Language input uses standard language codes, with examples including English, Japanese, German, and Hindi. Predefined topic categories cover technology, business, entertainment, sports, and world news.

Typical uses include creating daily briefings, researching current events, tracking a company or sector, monitoring policy topics, and adding live news context to a retrieval-augmented generation workflow.

How it works

The client connects to a remote streamable HTTP MCP endpoint. The server validates tool parameters, applies the requested region, language, topic, and freshness controls, and returns structured news data to the agent. The language model remains responsible for reasoning or summarizing the retrieved material.

NewzAI MCP Server MCP server exposes three focused tools:

• fetch_news_headlines requires a region and optionally accepts a language code. It is intended for fast, current headline retrieval.
• search_news_predefined_category requires one supported category and optionally accepts a region, language, and top_k article count. Its default region is India and its default result count is 20.
• search_news_for_any_category requires a custom topic or keyword. It also accepts region, language, top_k, and last_n_hours, allowing queries such as recent coverage of climate change or AI regulation.

Setup and configuration

Add the server as an HTTP MCP connection using this endpoint:

{
  "mcpServers": {
    "newzai": {
      "type": "http",
      "url": "https://api.newzai.ai/mcp/"
    }
  }
}

Google OAuth is required. Interactive clients prompt the user to sign in with Google on first use and maintain the authorized session afterward. The documented setup does not require an API key or manual key rotation. No environment variables are specified for this configuration.

The README identifies Claude Desktop, Cursor, VS Code Copilot, Windsurf, and other MCP-compatible clients as supported. The endpoint uses remote HTTP transport with a streamable HTTP manifest type.

Tools and capabilities

Use fetch_news_headlines for regional situational awareness and short “what happened” queries. Use the predefined-category tool when the request maps cleanly to one of the five fixed categories. Use the custom-topic tool for long-tail subjects, competitor monitoring, market research, or emerging themes.

Language selection supports multilingual retrieval, while last_n_hours can constrain custom-topic results to a recent time window such as 24 hours. top_k controls the requested number of articles for the two search tools.

Limitations and notes

Authentication depends on Google OAuth, so users must complete sign-in before using the tools. Headline retrieval requires one of the seven supported region slugs. Predefined-category searches are limited to technology, business, entertainment, sports, and world. Custom searches accept arbitrary topic text, but the available freshness control is documented for that tool rather than for headline retrieval or predefined-category searches.