Joke

A Model Context Protocol (MCP) server that provides access to the JokeAPI for retrieving jokes with various filtering options.

Quick Start

Add this MCP server to your client using the endpoint:

https://jokes.nico.dev/mcp

Your MCP client will automatically discover the get_joke tool and you can start fetching jokes immediately.

Features

• Single tool: get_joke - Fetch safe jokes from the JokeAPI
• Safe by default: Always uses safe-mode to filter out offensive content
• Multiple filtering options: Category, joke type, search terms
• Multiple jokes: Retrieve up to 10 jokes at once
• MCP compliant: Full JSON-RPC 2.0 implementation with session management

Installation

1. Clone the repository:

git clone <repository-url>
cd joke-mcp

2. Install dependencies:

composer install

Usage

The server exposes one tool: get_joke

Parameters

All parameters are optional:

• category (string): Joke category - Any, Programming, Misc, Pun, Spooky, Christmas
• type (string): Joke format - single (one-liner) or twopart (setup/delivery)
• contains (string): Search for jokes containing this text
• amount (integer): Number of jokes to retrieve (1-10)

Note: This server automatically uses safe-mode to ensure all jokes are appropriate and filter out offensive content.

Example Requests

Get a programming joke:

{
  "jsonrpc": "2.0",
  "id": "1",
  "method": "tools/call",
  "params": {
    "name": "get_joke",
    "arguments": {
      "category": "Programming"
    }
  }
}

Get multiple pun jokes:

{
  "jsonrpc": "2.0",
  "id": "2",
  "method": "tools/call",
  "params": {
    "name": "get_joke",
    "arguments": {
      "category": "Pun",
      "amount": 3
    }
  }
}

Search for jokes about cats:

{
  "jsonrpc": "2.0",
  "id": "3",
  "method": "tools/call",
  "params": {
    "name": "get_joke",
    "arguments": {
      "contains": "cat"
    }
  }
}

REST API Endpoint

In addition to the MCP interface, the server also provides a simple REST API endpoint for fetching jokes via HTTP GET requests.

GET /joke

Fetch jokes using query parameters:

# Get a random joke
GET https://jokes.nico.dev/joke

# Get a programming joke
GET https://jokes.nico.dev/joke?category=Programming

# Get a single-line joke
GET https://jokes.nico.dev/joke?type=single

# Get jokes containing "computer"
GET https://jokes.nico.dev/joke?contains=computer

# Get multiple jokes
GET https://jokes.nico.dev/joke?amount=5

# Combine parameters
GET https://jokes.nico.dev/joke?category=Pun&type=twopart&amount=3

Query Parameters

All parameters are optional:

• category: Joke category - Any, Programming, Misc, Pun, Spooky, Christmas
• type: Joke format - single (one-liner) or twopart (setup/delivery)
• contains: Search for jokes containing this text
• amount: Number of jokes to retrieve (1-10)

Response Format

Single joke:

{
  "joke": "Why do programmers prefer dark mode? Because light attracts bugs.",
  "type": "single",
  "category": "Programming"
}

Multiple jokes:

{
  "jokes": [
    {
      "text": "Why do programmers prefer dark mode? Because light attracts bugs.",
      "type": "single",
      "category": "Programming"
    },
    {
      "text": "How many programmers does it take to change a light bulb?\nNone, that's a hardware problem.",
      "type": "twopart",
      "category": "Programming"
    }
  ]
}

Error response:

{
  "error": "Error message here"
}

API Integration

This server integrates with the JokeAPI v2 which provides:

• 120 requests per minute rate limit
• No authentication required
• Multiple response formats (JSON default)
• Safe-mode enabled by default to filter out offensive content

Technical Details

• PHP: Requires PHP 8.0+
• HTTP Client: Uses Guzzle HTTP for reliable API requests
• Session Management: Implements MCP session handling with file-based storage
• Security: Origin validation, proper error handling, and safe-mode enforcement
• MCP Protocol: Full compliance with MCP specification

File Structure

src/
├── MCPServer.php          # Main MCP server implementation
data/
├── mcp_sessions.json      # Session storage (created automatically)
composer.json              # Dependencies and autoloading

Development

The server follows MCP protocol standards and can be integrated with any MCP-compatible client. It handles:

• Tool discovery via tools/list
• Tool execution via tools/call
• Session management with secure session IDs
• Proper JSON-RPC 2.0 response formatting
• Error handling for network and API issues