
Wraps the icanhazdadjoke.com API and exposes three straightforward tools: random_joke for a single joke, search_jokes to filter by keyword or topic, and get_joke to retrieve by ID. No authentication required. Runs through Pipeworx's streamable HTTP gateway, which also offers an ask_pipeworx interface that lets you query in natural language instead of calling tools directly. Useful when you want to lighten the mood in a CLI tool, add humor to a chatbot, or test MCP integration without dealing with API keys. Part of a larger gateway that connects to 673+ data sources, so you can add it standalone or access it through the full Pipeworx setup.
Dad Jokes MCP — wraps icanhazdadjoke.com (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
random_joke | Fetch one random dad joke from icanhazdadjoke.com. Returns joke text and alphanumeric ID. |
search_jokes | Search dad jokes by keyword or topic. Returns matching jokes with IDs and text. |
get_joke | Retrieve a specific dad joke by ID. Returns the full joke text. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"dadjokes": {
"url": "https://gateway.pipeworx.io/dadjokes/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/dadjokes/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Dadjokes data" })
The gateway picks the right tool and fills the arguments automatically.
MIT