NYT Cooking MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NYT_USER_ID | No | The regi_id value from the regi_cookie, used with NYT_S_COOKIE for authentication. | |
| NYT_S_COOKIE | No | Value of the NYT-S cookie from cooking.nytimes.com, used to authenticate for saved recipes. | |
| NYT_MCP_ALLOWED_HOSTS | No | Comma-separated allowed hosts for HTTP server (e.g., 'your.server.ip:*'). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_recipesA | Search NYT Cooking for recipes matching a natural-language query. Args: query: Search terms, e.g. "chicken parmesan" or "vegetarian chili". Returns a list of results with id, name, url and author. Use the id with get_recipe to fetch full ingredients and steps. |
| get_recipeA | Fetch full details for a single NYT Cooking recipe by its numeric id. Args: recipe_id: The recipe id, e.g. "1019049" (from a search result or URL). Returns name, author, time, servings, rating, description, ingredients and step-by-step instructions. |
| list_saved_recipesA | List recipes saved in the user's NYT Cooking recipe box. Requires a configured user id and a valid session cookie (see Args: page: 1-indexed page number. per_page: Number of results per page (default 48). |
| loginA | Store your NYT Cooking credentials so the server stays logged in. NYT Cooking has no OAuth, so credentials are harvested once from your logged-in browser and persisted server-side (like a session token):
The credentials are written to the server's credentials file and verified with a live request before returning. |
| logoutA | Delete the stored NYT Cooking credentials from the server. |
| auth_statusA | Report whether NYT credentials (session cookie and user id) are configured. Does not reveal the values. Useful for diagnosing auth_required errors. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a distinct purpose: authentication status, login/logout, search, recipe retrieval, and saved recipes listing. No two tools perform overlapping functions.
All tools use consistent snake_case naming (e.g., search_recipes, get_recipe, list_saved_recipes), following a clear verb_noun pattern.
Six tools cover the essential operations for a recipe service (auth, search, read, list saved) without unnecessary bloat. The count is appropriate for the domain.
Core workflows are covered: login, search, get recipe, list saved recipes, and logout. However, there is no tool to save a recipe or manage the saved list (e.g., remove), which are minor gaps for a complete lifecycle.