nyt-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your New York Times 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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_articlesA | Search NYT articles by keyword and optional filters. Args: ctx: MCP context (injected automatically). query: Search query string. filter_query: Lucene-syntax filter (e.g. 'section.name:"Books"'). begin_date: Start date in YYYYMMDD format. end_date: End date in YYYYMMDD format. sort: Sort order - 'newest', 'oldest', or 'relevance'. page: Page number (0-indexed, max 100). Returns: Formatted search results. |
| get_top_storiesC | Get the current top stories for a given NYT section. Args: ctx: MCP context (injected automatically). section: Section name (e.g. 'home', 'world', 'science', 'politics'). Returns: Formatted list of top stories. |
| get_most_popularB | Get the most popular NYT articles (emailed, shared, or viewed). Args: ctx: MCP context (injected automatically). popularity_type: One of 'emailed', 'shared', or 'viewed'. period: Time period in days - 1, 7, or 30. Returns: Formatted list of popular articles. |
| get_newswireB | Get the latest articles from the Times Newswire (live stream). Args: ctx: MCP context (injected automatically). source: Content source - 'all', 'nyt', or 'inyt'. section: Section name, or 'all' for everything. Returns: Formatted list of recent articles. |
| get_bestsellersA | Get the NYT Best Sellers list. Args: ctx: MCP context (injected automatically). list_name: List slug (e.g. 'hardcover-fiction', 'paperback-nonfiction'). date: Published date (YYYY-MM-DD) or 'current' for the latest. Returns: Formatted best-seller list. |
| get_archiveB | Get article metadata from the NYT Archive for a given month. Results are capped at 50 articles to keep context manageable. Args: ctx: MCP context (injected automatically). year: Year (>= 1851). month: Month (1-12). Returns: Formatted list of archived articles. |
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 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.