# angheljf/nyt [Health: Active]

**Category:** 🔎 Search & Data Extraction  
**Repository:** https://github.com/angheljf/nyt  
**GitHub Stars:** 19  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/angheljf-nyt

## Description
Search articles using the NYTimes API

## Tools
Capabilities this server exposes over MCP:

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

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "nyt": {
    "command": "npx",
    "args": ["-y","@smithery/cli"],
    "env": {
      "NYTIMES_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `NYTIMES_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What angheljf/nyt MCP server does

The angheljf/nyt MCP server lets an MCP-compatible client search New York Times articles published within the previous 30 days. Its single operation accepts a required keyword and returns matching article information, including the title, abstract, URL, publication date, and author.

This fits workflows that need current or recently published NYTimes content without building a separate API client into an agent application. The available search window is fixed at 30 days, so it is intended for recent-article lookup rather than historical archive research.

## How it works

The server is written in TypeScript and communicates with MCP clients through standard input and output. When a client invokes the search operation, the server uses the New York Times API to look up articles matching the supplied keyword.

The exposed tool is named `search_articles`. Its required input is `keyword`. Results are returned as a list of articles with the fields described by the project: title, abstract, URL, published date, and author.

## Setup and configuration

A New York Times API key is required. Store it in a `.env` file at the project root or provide it in the MCP client configuration under the `NYTIMES_API_KEY` environment variable.

For local development, install the project dependencies with `npm install`, then compile the TypeScript source using `npm run build`. The generated server can be started with `node build/index.js`. The README also provides `npm run watch` for development with automatic rebuilding.

Claude Desktop can connect to the local process by adding an MCP server entry that runs Node against `build/index.js` and passes `NYTIMES_API_KEY` in the environment. The repository also documents Smithery installation for Claude Desktop, but that route is separate from running the project directly from a local checkout.

## Tools and capabilities

The angheljf/nyt MCP server exposes one tool:

- `search_articles`: searches NYTimes articles from the last 30 days using a required keyword and returns article metadata.

The returned metadata can support agent responses that cite or summarize recent New York Times coverage, provided the client uses the returned URLs and text appropriately.

## Limitations and notes

Only one tool is documented, and it searches by keyword within a 30-day period. The provided material does not describe filters for section, author, language, date ranges, pagination, or article body retrieval.

The server depends on access to the New York Times API and therefore cannot perform searches without a configured API key. It uses stdio transport, so local process configuration is required unless another supported deployment mechanism is added. For troubleshooting, the project includes an `npm run inspector` script that launches the MCP Inspector workflow described in the README.

_Full upstream README: https://allmcps.com/mcp/angheljf-nyt/readme_