mcpField
N
NerdyChefs Prompts

NerdyChefs Prompts

Local
nerdychefs.aiAI & Agents2Updated 5w ago

About NerdyChefs Prompts

NerdyChefs Prompts is an MCP server for searching and browsing the free NerdyChefs.ai prompt library. It serves prompt and pack details on demand, with results and filters processed locally.

Key features

  1. 01Search prompts with filters
  2. 02Retrieve full prompt text
  3. 03Browse prompt packs
  4. 04List categories, personas, and tags
  5. 05Cache fetched data for 60 minutes

Use cases

  1. 01Finding prompts for a task
  2. 02Opening a prompt pack and its contents
  3. 03Exploring prompts by category or persona

MCP support

Exposes prompt search, prompt and pack retrieval, and library taxonomy tools to MCP clients. It also provides a pack resource at `nerdychefs://pack/{slug}`.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"mayeu20-nerdychefs": {
"command": "npx",
"args": [
"-y",
"nerdychefs-mcp"
]
}
}
}
Run commandnpx -y nerdychefs-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmnerdychefs-mcp0.1.2

Tools

8

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
tagstringNo
limitintegerNo
querystringYes
personastringNo
categorystringNo
include_prompt_textbooleanNo

Details

From the project README

nerdychefs-mcp

An MCP server that gives your assistant access to the free prompt library at NerdyChefs.ai. Search for a task, open a pack, or pick a random prompt to try.

It runs over stdio and fetches prompts when you first need them. Data stays in memory for 60 minutes. Requires Node 20 or newer.

Tools

NameArgumentsWhat you get
search_promptsquery (2 to 200 characters); optional category, persona, tag, limit (1 to 25, default 10), include_prompt_text (default false)Ranked prompt summaries, total matches, and links.
get_promptid (integer)One prompt with its full text and links.
random_promptOptional category, persona, tagA random prompt with full text and the pool size.
list_packsOptional category, query, limit (1 to 120, default 50)Packs ordered by title, with descriptions and links.
get_packid (slug or exact title); optional include_prompts (default true), include_prompt_text (default false)Pack details, sections, and optional prompts ordered by ID.
list_categoriesNoneCategories, subcategories, and prompt counts.
list_personasOptional top (1 to 873, default 50), queryPersonas ordered by count, then name.
list_tagsOptional top (1 to 500, default 50), queryTags ordered by count, then name.

Category, persona, and tag filters use case-insensitive exact matches. Pack queries search titles and descriptions. Persona and tag queries match part of a name. Search results omit prompt text unless requested. Every argument above also carries its own description in the tool schema, so your client can show you the same detail inline.

Two things catch people out, and both fail quietly rather than with an error:

  • Filter on the category NAME, not its id. list_categories returns both, and only Engineering & DevOps matches. The slug form engineering-devops returns an empty result.
  • get_prompt ids are positions in the published prompt file, not ids from the website. Use an id from search_prompts, random_prompt or get_pack in the same session. An id copied from a nerdychefs.ai page, or saved from last week, can name a different prompt.

The resource nerdychefs://pack/{slug} returns the same JSON as get_pack with prompt summaries and no prompt text.

Installation for Claude Desktop

Add this entry to your MCP configuration, then restart the client:

{
  "mcpServers": {
    "nerdychefs": {
      "command": "npx",
      "args": ["-y", "nerdychefs-mcp"]
    }
  }
}

Installation for Claude Code

claude mcp add nerdychefs -- npx -y nerdychefs-mcp

Installation for Cursor

Add this to your MCP configuration:

{
  "mcpServers": {
    "nerdychefs": {
      "command": "npx",
      "args": ["-y", "nerdychefs-mcp"]
    }
  }
}

Installation for Codex CLI

codex mcp add nerdychefs -- npx -y nerdychefs-mcp

Configuration

NERDYCHEFS_API_BASE defaults to https://www.nerdychefs.ai/api. Set it in the server's environment to change the API path. Remote URLs must use HTTPS on www.nerdychefs.ai. Local HTTP addresses are accepted for fixture tests. Redirects are refused.

Files load on demand and are cached separately for 60 minutes. Failed requests get one retry. A failed tool call names the file that could not load.

Privacy

The only remote host the server talks to is www.nerdychefs.ai. It downloads public JSON files. Searches and filters run locally. No user queries, prompt inputs, or client conversations are sent to the site.

Nothing is logged or sent anywhere else. There is no telemetry, analytics, or runtime disk cache. Local fixture tests use a loopback HTTP server. Returned website links include the fixed utm_source=mcp, utm_medium=tool, and utm_campaign=nerdychefs_mcp parameters.

Attribution

Prompts from NerdyChefs.ai. Prompts are served live from nerdychefs.ai and remain that site's content. Each prompt result includes attribution and links to its prompt and pack pages. The package does not include the prompt corpus.

Development

pnpm install
pnpm build
pnpm test
NERDYCHEFS_LIVE=1 pnpm test

The regular tests use small local fixtures. The live smoke test runs only when NERDYCHEFS_LIVE=1. Start the compiled server with node dist/index.js, or use pnpm dev while editing. Standard output is reserved for MCP messages.

Licence

The server code is MIT licensed. Copyright 2026 Mathieu Kessler. See LICENSE. This licence covers the server code. Prompts remain NerdyChefs.ai content.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.