Skip to main content
Glama
enesjakozh
angheljf

NYTimes Article Search MCP Server

by angheljf
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

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

ParametersJSON Schema
NameRequiredDescriptionDefault
keywordYesKeyword to search for in articles

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the 30-day time constraint, which is useful, but fails to describe critical behaviors such as response format, pagination, error handling, or any rate limits. For a search tool with zero annotation coverage, this leaves significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core functionality without unnecessary words. Every part ('Search NYTimes articles from the last 30 days based on a keyword') contributes directly to understanding the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It covers the basic purpose and time constraint but omits details on behavioral traits, response structure, and usage guidelines. For a search tool, this leaves the agent with insufficient context to use it effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the parameter 'keyword' well-documented in the schema. The description adds minimal value by implying keyword-based filtering but doesn't provide additional semantics like search syntax or examples. Baseline 3 is appropriate when the schema handles parameter documentation effectively.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Search NYTimes articles') and resource ('articles'), specifying the scope ('from the last 30 days') and filtering criteria ('based on a keyword'). It lacks sibling tool differentiation, but since there are no sibling tools, this doesn't reduce clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides basic context (searching recent articles by keyword) but offers no explicit guidance on when to use this tool versus alternatives, prerequisites, or exclusions. Without siblings, the need for differentiation is lower, but it still lacks usage context like rate limits or authentication needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
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
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/angheljf/nyt'

If you have feedback or need assistance with the MCP directory API, please join our Discord server