How far back does the NYTimes archive go?

The article search API provides access to articles dating back to 1851. It is one of the most comprehensive historical newspaper archives available.

Can I get the actual text of the articles?

The API provides the headline, abstract (summary), snippet, and URL to the full article on NYTimes.com. Full text is not included in the API response but can be accessed via the provided link.

What sections are available for Top Stories?

You can access almost any section of the NYTimes, including home, world, politics, business, technology, sports, arts, health, and science. Use the get_sections tool to see the full list.

New York Times MCP Server for CrewAI 9 tools — connect in under 2 minutes

Name: New York Times
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 9 Tools Framework

Connect your CrewAI agents to New York Times through the Vinkius — pass the Edge URL in the `mcps` parameter and every New York Times tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="New York Times Specialist",
    goal="Help users interact with New York Times effectively",
    backstory=(
        "You are an expert at leveraging New York Times tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in New York Times "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 9 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About New York Times MCP Server

Connect the New York Times API to any AI agent and unlock access to over 170 years of journalism — including breaking news, historical archives, best-seller lists, and cultural reviews.

When paired with CrewAI, New York Times becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call New York Times tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Top Stories — Get the latest top stories for any section (World, Politics, Tech, Sports, etc.)
Article Search — Search the complete archive from 1851 to the present day with keywords and date filters
Most Popular — See what readers are emailing, sharing, and viewing the most
Best-Seller Lists — Retrieve current and historical book best-seller lists
Movie Reviews — Access thousands of movie reviews and critic summaries
Section Discovery — List all available sections and topics covered by the NYTimes

The New York Times MCP Server exposes 9 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect New York Times to CrewAI via MCP

Follow these steps to integrate the New York Times MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 9 tools from New York Times

Why Use CrewAI with the New York Times MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with New York Times through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

New York Times + CrewAI Use Cases

Practical scenarios where CrewAI combined with the New York Times MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries New York Times for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries New York Times, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain New York Times tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries New York Times against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

New York Times MCP Tools for CrewAI (9)

These 9 tools become available when you connect New York Times to CrewAI via MCP:

get_archive

Get all articles for a specific month

get_book_lists

"list_name_encoded" is the list slug (e.g., "hardcover-fiction"). Optional date is YYYY-MM-DD. Get current or historical best-seller lists

get_most_emailed

Period can be 1, 7, or 30 days. Get the most emailed articles for a specific period

get_most_shared

Period can be 1, 7, or 30 days. Get the most shared articles on social media

get_most_viewed

Get the most viewed articles

get_movie_reviews

Optional "query" filters by movie title. Search for movie reviews in the NYTimes archive

get_sections

List all available news sections

get_top_stories

g., home, world, politics, technology, sports). Use get_sections to see available options. Get top stories for a specific section

search_articles

Use "q" for keywords, "begin_date" and "end_date" for date ranges (YYYYMMDD), and "sort" for "newest", "oldest", or "relevance". Search for articles using keywords, date ranges, and sorting

Example Prompts for New York Times in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with New York Times immediately.

"Show me today's top world news."

"What is the #1 Hardcover Fiction book this week?"

"Find movie reviews for 'The Godfather'."

Troubleshooting New York Times MCP Server with CrewAI

Common issues when connecting New York Times to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

New York Times + CrewAI FAQ

Common questions about integrating New York Times MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.