Skip to main content
Glama
NYTimes Article Search MCP Server

NYTimes Article Search MCP Server

by angheljf

NYTimes Article Search MCP Server

Trust Score

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

NYTimes Article Search

Features

Tools

  • search_articles - Search NYTimes articles from the last 30 days based on a keyword

    • Takes keyword as a required parameter

    • Returns a list of articles with title, abstract, URL, published date, and author

Related MCP server: image-reader MCP Server

Development

Install dependencies:

npm install

Build the server:

npm run build

For development with auto-rebuild:

npm run watch

Debugging

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 inspector

The 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 claude

Manual 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_here

Running the Server

After building the project, you can run the server with:

node build/index.js

The server will start and listen for MCP requests over stdio.

License

This project is licensed under the MIT License.

Available Tools

1 tool
search_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

    B3.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness2/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers