NYTimes Article Search MCP Server
The NYTimes Article Search MCP Server allows you to search for New York Times articles published within the last 30 days. With this server, you can:
Search for articles using specified keywords
Retrieve article details including title, abstract, URL, published date, and author information
Integrate with Claude Desktop using Smithery or manual configuration
Access debugging support via the MCP Inspector during development
Utilize the New York Times API for fetching article data
Enables configuration through environment variables stored in a .env file, specifically for storing and accessing the New York Times API key.
Provides tools for searching New York Times articles from the last 30 days based on keywords, returning article details including title, abstract, URL, published date, and author.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@NYTimes Article Search MCP Server search for recent articles about climate change"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
NYTimes Article Search MCP Server
This is a TypeScript-based MCP server that allows searching for New York Times articles from the last 30 days based on a keyword. It demonstrates core MCP concepts by providing:
Tools for searching articles
Integration with the New York Times API

Features
Tools
search_articles- Search NYTimes articles from the last 30 days based on a keywordTakes
keywordas a required parameterReturns a list of articles with title, abstract, URL, published date, and author
Related MCP server: image-reader MCP Server
Development
Install dependencies:
npm installBuild the server:
npm run buildFor development with auto-rebuild:
npm run watchDebugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:
npm run inspectorThe Inspector will provide a URL to access debugging tools in your browser.
Installation
Installing via Smithery
To install NYTimes Article Search for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install nyt --client claudeManual Installation
To use with Claude Desktop, add the server config:
On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"nyt": {
"command": "node",
"args": ["path/to/your/build/index.js"],
"env": {
"NYTIMES_API_KEY": "your_api_key_here"
}
}
}
}Environment Variables
Create a .env file in the root of your project and add your New York Times API key:
NYTIMES_API_KEY=your_api_key_hereRunning the Server
After building the project, you can run the server with:
node build/index.jsThe server will start and listen for MCP requests over stdio.
License
This project is licensed under the MIT License.
Available Tools
1 toolsearch_articlesC
Search NYTimes articles from the last 30 days based on a keyword
Inputs: keyword (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'search_articles' has a clearly defined and distinct purpose.
The single tool name follows a clear verb_noun pattern ('search_articles'), and with only one tool, there is no inconsistency to evaluate. The naming is straightforward and appropriate.
One tool is too few for a server with the apparent scope of 'NYTimes Article Search,' which suggests a domain that could benefit from additional operations like filtering by date, retrieving article details, or accessing different sections. A single search tool feels thin and limits functionality.
The tool surface is severely incomplete for the domain. While search is a core function, there are obvious gaps such as the inability to retrieve full article content, filter beyond keywords, or access other NYTimes data like sections or authors. This will likely cause agent failures when more comprehensive interactions are needed.
Maintenance
Related MCP Connectors
A simple Typescript MCP server built using the official MCP Typescript SDK and smithery/cli. This…
An MCP server that provides congressional transcripts
MCP server for searching Airweave collections with natural language queries.
NYT MCP — wraps The New York Times Developer APIs (developer.nytimes.com)
Related MCP Servers
- FlicenseBqualityDmaintenanceA TypeScript-based MCP server that implements a simple notes system, allowing users to create, access, and generate summaries of text notes.123-
- FlicenseAqualityDmaintenanceA TypeScript-based MCP server that implements a simple notes system, allowing creation and management of text notes with URIs and metadata.4-
- FlicenseBqualityDmaintenanceA TypeScript-based MCP server that implements a simple notes system, allowing users to create, access, and generate summaries of text notes.23-
- AlicenseDqualityAmaintenanceA TypeScript-based MCP server that enables users to query financial news, stock data, and index information while managing text notes with creation and summarization capabilities.5874MIT