nyt-mcp
Related Servers
Alternatives to nyt-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that provides access to the New York Times Newswire API, allowing agents to retrieve real-time news updates and content from the New York Times.-
- AlicenseBqualityDmaintenanceThis is a TypeScript-based MCP server that allows searching for New York Times articles from the last 30 days based on a keyword.111 npm19MIT
- AlicenseNot gradedqualityDmaintenanceA TypeScript-based MCP server for NewsAPI, enabling search for news articles, fetch top headlines, and discover sources through natural language.16 npmMIT
- AlicenseNot gradedqualityCmaintenanceWraps The New York Times Developer APIs, enabling natural language querying of NYT data through the Pipeworx MCP gateway.2 npm1MIT
- FlicenseNot gradedqualityDmaintenanceA Multi-Agent Conversation Protocol server that provides access to the New York Times Most Popular API, allowing agents to interact with NYT's most viewed, shared, and emailed content.-
- FlicenseNot gradedqualityFmaintenanceMCP server providing access to the GNews API for fetching news articles and headlines. Supports search and top headlines with advanced filtering by language, country, category, and date.1-
TDQS
Scored across 6 tools
Each tool maps to a distinct NYT data source (search, top stories, most popular, newswire, bestsellers, archive), so boundaries are largely clear. The only mild overlap is among search_articles, get_top_stories, and get_newswire, which all return article lists but are distinguished by source semantics.
Five tools use a clean get_<noun> pattern (get_top_stories, get_most_popular, get_newswire, get_bestsellers, get_archive), and search_articles is a sensible, readable variation on the verb for a query operation. The convention is predictable throughout.
Six tools is well-scoped for the NYT API surface, with each tool earning its place by covering a distinct endpoint-like capability. No redundant or filler tools.
The set covers the major NYT read paths: keyword search, curated stories, popularity, newswire, bestsellers, and historical archive. Minor gaps exist (e.g., no single-article fetch by URL/ID, no byline/review endpoints), but core discovery workflows are fully served.