AllNewsAPI MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALLNEWSAPI_KEY | No | Your AllNewsAPI key. Can also be provided via --apikey command-line argument. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-newsB | Search for news articles using various parameters including keywords, date ranges, and filters |
| headlinesB | Get top headlines with optional filtering by country, category, and language |
| usageA | Check your current API plan, usage limits, and remaining quota |
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
search-news and headlines are clearly distinct in purpose—one returns filtered article search results, the other returns top headlines by source/category. usage is completely separate, so there is little risk of selecting the wrong tool.
Tool names are readable but follow mixed conventions: search-news uses a verb-noun pattern, while headlines and usage are bare nouns. This is not chaotic, but the naming style is inconsistent across the set.
Three tools is a reasonable minimal set for a news API server covering search, headlines, and account usage. It is slightly thin but appropriate for the apparent scope.
The core news retrieval operations are covered, and usage is a nice operational addition. However, a typical news API also exposes available sources or categories, and that capability is missing, leaving a notable gap for agents that need source metadata.