Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-bored suggest a random activity"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Bored MCP — wraps Bored API (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
Tool | Description |
| Get a random activity suggestion to cure boredom. Returns activity name, type, participant count, and price range. |
| Find a random activity by category (e.g., 'cooking', 'sport', 'relaxation'). Returns activity name, type, participants needed, and price range. |
| Find a random activity for a specific group size (e.g., 1 for solo, 4 for group). Returns activity name, type, and price range. |
Related MCP server: Random Word By Api Ninjas
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"bored": {
"url": "https://gateway.pipeworx.io/bored/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/bored/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 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
curl -X POST https://gateway.pipeworx.io/v1/tools/random_activity \
-H 'Content-Type: application/json' \
-d '{}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/random_activity. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"bored": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-bored"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-boredIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
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 Bored data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
Real local places, events, and movie/TV picks, plus decision-maker games (wheel, dice, bracket).
Get a random dad joke or search by keyword to fit any moment. Retrieve specific jokes by ID for re…
Plans a whole day out in any city, matched to the weather, your mood and diet.
Find group trips and day outs to join, events in a city, and where to go by weather and budget.