Claude MarketplacesSubmit
hamzaaamin avatar

Get Joke

hamzaaamin/get-joke

A lightweight server that adds a single `get_joke` tool to your Claude workflow, returning random programming jokes in JSON format. Built in Node.js with stdio transport, it's the kind of thing you'd drop into a dev environment when you want to inject a little levity into automated workflows or test integrations without touching production APIs. The entire setup is straightforward: install from npm as `@hamzaamin221/get-joke-mcp`, run it, and call the tool. No configuration, no external dependencies, no rate limits. Useful for demos, testing MCP tooling, or just breaking up long coding sessions with dad jokes about why programmers prefer dark mode.

tool
1
transport
STDIO
last updated
Mar 11, 2026
View on GitHub

Tools

1 tools

Public tool metadata for what this MCP can expose to an agent.

get_jokeReturns a random programming joke as JSON with a joke field.

Returns a random programming joke as JSON with a joke field.

No parameter schema in public metadata yet.

Sponsors

Promote your product hereReach 125k+ visitors monthlyPromote your product hereReach 125k+ visitors monthlyAgent CaffeineSponsoredClose your lid, come back to finished workSnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthlyWaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthlyknobsSponsoredSee your site on any phone, any day, in any language

Readme

Get Joke MCP Server

Minimal Model Context Protocol (MCP) server (Node.js) that exposes one tool: get_joke.

Setup

npm install

Run

node index.js

Or:

npm start

Test (without Inspector)

This repo includes a tiny SDK-based client that spawns the server over stdio, lists tools, and calls get_joke:

npm run test:mcp

Tool response shape

The get_joke tool returns JSON like:

{
  "joke": "Why do programmers prefer dark mode? Because light attracts bugs."
}

Publish to the MCP Registry (official)

The official MCP Registry stores metadata only, so you must publish the package to npm first.

  1. Publish to npm (once):
npm adduser
npm publish --access public
  1. Publish metadata to the MCP Registry:
brew install mcp-publisher
mcp-publisher login github
mcp-publisher publish

Notes:

  • package.json includes mcpName and server.json uses the same name (required for verification).
  • If you change the version, bump it in both package.json and server.json (and republish to npm).

Details

Repository
github.com/hamzaaamin/get-joke
Package
@hamzaamin221/get-joke-mcp
Transport
STDIO
Registry
MCP registry, active