
Wraps the Advice Slip API to surface random advice, keyword search, and ID-based retrieval through three simple tools. You get random_advice for a spontaneous slip, search_advice to query by topic like "confidence" or "relationships", and get_advice to pull a specific slip by its numeric ID. No authentication required. Part of the Pipeworx gateway ecosystem, so you can either connect to this standalone endpoint or fold it into a larger gateway setup with 673+ other data sources. Useful for chatbots, creative prompts, or any project that needs a quick injection of crowd-sourced wisdom without managing API keys or rate limits.
Advice MCP — wraps Advice Slip API (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
random_advice | Get a random piece of advice. Returns the advice text and slip ID for reference or follow-up queries. |
search_advice | Search for advice by keyword or phrase (e.g., "confidence", "relationships"). Returns matching advice slips with text and IDs. |
get_advice | Get a specific advice slip by its numeric ID (e.g., "42"). Returns the full advice text. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"advice": {
"url": "https://gateway.pipeworx.io/advice/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/advice/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 Advice data" })
The gateway picks the right tool and fills the arguments automatically.
MIT