News API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEWS_API_KEY | Yes | Your News API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-newsC | Search for news articles on any topic |
| get-top-headlinesC | Get top headlines by country, category, or source |
| get-news-sourcesC | Get available news sources |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: retrieving sources, top headlines by criteria, and searching articles. No overlap.
All tool names follow a consistent verb_noun pattern (get-news-sources, get-top-headlines, search-news), using snake_case.
3 tools is slightly minimal but appropriate for a focused news API server. Could include more endpoints but not excessive.
Covers core news retrieval tasks (sources, headlines, search). Missing explicit article retrieval by ID, but still functional for typical use cases.