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-chucknorris tell me a random Chuck Norris joke"
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.
Chuck Norris MCP — wraps chucknorris.io (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tool | Description |
| Fetch one random Chuck Norris joke from chucknorris.io. Returns joke text, unique ID, category list, and permalink URL. |
| Search Chuck Norris jokes by keyword. Returns matching jokes with text and IDs. |
| List all available Chuck Norris joke categories (e.g., 'nerdy', 'sport'). Use with joke_by_category to fetch jokes. |
| Get a random Chuck Norris joke from a specific category. Returns joke text and ID. |
Related MCP server: Jokes MCP Server
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"chucknorris": {
"url": "https://gateway.pipeworx.io/chucknorris/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/chucknorris/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 Chucknorris data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
Gateway between LLM agents and world data through eight tools and a bundled endpoint catalog.
Provides cloud browser automation capabilities using Stagehand and Browserbase, enabling LLMs to i…
Discover, inspect and run 63,000+ agent tools from one balance. Pay per call, no subscriptions.
Web search and page-reading for AI agents. One-click OAuth connect, or a Caesar API key.
