Tarot

What tarot MCP server does

The tarot MCP server exposes tarot card data through the Model Context Protocol. Its source is tarotapi.dev, which provides the card content without authentication. The available card set contains the full 78-card deck, including major and minor arcana. Responses include card names, short identifiers, suits, arcana type, upright meanings, reversed meanings, and descriptions where applicable.

The server is intended for MCP-compatible AI clients and applications that need to select, inspect, or find tarot cards.

How it works

A client can connect to the hosted MCP endpoint at https://gateway.pipeworx.io/tarot/mcp. The endpoint lists the tarot tools together with shared Pipeworx gateway tools. Its initialize response is the authoritative source for the tools exposed by that connection, because the gateway scope may change. The shared tools can also route broader questions through ask_pipeworx.

The same package can run as a local stdio process. In that mode, MCP messages use standard input and output, and the process exposes only the tarot pack’s four tools. This avoids a Pipeworx gateway round trip and does not require a Pipeworx account.

A client can also call the hosted tools over HTTP without using an MCP client. For example, the gateway exposes tarot_random_card under /v1/tools/, and tool details can be inspected through the corresponding GET endpoint.

Setup and configuration

For a hosted connection, add the following MCP server configuration to a compatible client:

{
  "mcpServers": {
    "tarot": {
      "url": "https://gateway.pipeworx.io/tarot/mcp"
    }
  }
}

For local stdio use, run the published package with npx:

{
  "mcpServers": {
    "tarot": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-tarot"]
    }
  }
}

You can verify that the local process starts with npx -y @pipeworx/mcp-tarot. No environment variables are documented.

Tools and capabilities

The tarot MCP server provides these tools:

• random_card selects one card from the 78-card deck and returns its name, short ID, suit, arcana type, upright meaning, reversed meaning, and description.
• draw_cards accepts a count from 1 through 78 and returns the corresponding random-card records with the same fields.
• search_cards finds cards by keyword, matching card names and descriptions.
• get_card retrieves one card using its short identifier, such as ar00 for The Fool, ar01 for The Magician, or wap01 for Ace of Wands.

The gateway can additionally expose shared Pipeworx tools, including ask_pipeworx, discover_tools, search_within, and remember/recall. Those tools belong to the gateway layer rather than the local tarot package.

Limitations and notes

The hosted pack endpoint includes shared gateway tools in addition to the tarot tools, so its listed tool count is higher than four. The standalone process does not include those shared tools. Both hosted URLs described in the documentation reach the same Pipeworx gateway and data sources; the pack URL determines which tools are listed directly.

The documentation does not specify card artwork, reversed-card randomization behavior, configurable decks, authentication settings, rate limits, or a persistent data store. It also does not state that search supports fields beyond names and descriptions. Use the short identifiers supplied by the card data when calling get_card.