dad-jokes

Dad Jokes MCP Server is a TypeScript-implemented MCP server that serves a curated collection of dad-joke generation tools. It supports multiple joke styles, topic-based generation, random joke creation, a rating system, and a category browser, all exposed through the MCP protocol. Using this server, clients can request prompts like generate-dad-joke with a specific topic and style, fetch random jokes, rate jokes, and discover joke categories. The server is designed to be integrated with MCP clients (such as Claude Desktop or standard MCP clients) via the standard stdio transport, or run directly with Node in development environments. The tooling is organized to be extensible, with prompts, tools, and error handling built into a clean TypeScript codebase to keep interactions robust and type-safe.

Prerequisites:

• Node.js >= 18.0.0
• npm or yarn
• TypeScript (optional for development)

Installation steps:

1. Clone the repository:

# Clone the repository
git clone https://github.com/OrenGrinker/dad-jokes-mcp-server.git
cd dad-jokes-mcp-server

2. Install dependencies:

npm install

3. Build the project (produces dist/):

npm run build

4. Run the server locally:

npm start

Development setup (optional):

# Start in development mode with auto-rebuild (if configured)
npm run dev
# Linting
npm run lint
# Run tests (if implemented)
npm test
# Clean build directory
npm run clean

Usage after install:

• Start the server and connect via MCP clients using the stdio transport or by invoking node dist/index.js directly in a test scenario.
• Example client initialization payloads and typical workflow are documented in the README under Integration and Usage sections.

Notes and tips:

• This server is built for Node.js environments. The MCP entry point is dist/index.js, produced by the TypeScript build process. -Environment variables: you can enable debug logging with DEBUG and adjust log verbosity with LOG_LEVEL. These are optional and safe to omit in production. -If you customize or extend the server (categories, styles, or tools), remember to re-run npm run build before starting in production. -Common issues: ensure the dist/ directory exists after build; verify Node.js version is >= 18.0.0; confirm MCP client configuration paths when integrating with external clients. -For integration, you can either embed the server via the standard MCP client interface or use the provided Claude Desktop integration snippet as a reference for structuring your own config.