
Wraps tarotapi.dev to give Claude three operations: drawing a single random card with upright and reversed meanings, pulling multiple cards in one go (up to 78), and searching the deck by keyword against names and descriptions. No auth required. Runs through Pipeworx's gateway, which hosts 673+ data sources behind a single MCP endpoint. You can either call the tarot tools directly or use the ask_pipeworx question interface to let the gateway route your natural language query to the right tool. Useful if you're building conversational apps that need mystical flavor or want to prototype card reading interfaces without standing up your own tarot API wrapper.
Tarot MCP — wraps tarotapi.dev (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
random_card | Draw one random tarot card from the full 78-card deck. Returns card name, short ID, suit, type (major/minor arcana), upright meaning, reversed meaning, and description. |
draw_cards | Draw a spread of 1–78 random tarot cards (pass count). Returns each card's name, short ID, suit, type, upright meaning, reversed meaning, and description. |
search_cards | Search tarot cards by keyword — matches against card names and descriptions. |
get_card | Get a specific tarot card by its short name identifier (e.g. "ar01" for The Magician, "ar00" for The Fool, "wap01" for Ace of Wands). |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"tarot": {
"url": "https://gateway.pipeworx.io/tarot/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/tarot/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 Tarot data" })
The gateway picks the right tool and fills the arguments automatically.
MIT