Tarot Draw

What Tarot Draw does

Tarot Draw MCP server gives an MCP-compatible AI client access to a tarot card draw and interpretation. Its primary operation, tarot_draw_pull, selects a card from a 78-card deck and interprets it in relation to the caller's situation.

The package is provided through Pipeworx, which exposes the tool either as a scoped gateway endpoint or as a local MCP process. The scoped gateway connection can also show shared Pipeworx tools, while the local process is limited to this pack's own tool.

How it works

A client can connect to https://gateway.pipeworx.io/tarot-draw/mcp using its MCP configuration. That endpoint returns tarot_draw_pull along with shared gateway tools such as ask_pipeworx, discover_tools, search_within, and remember/recall. The exact tool scope is reported by the connection's initialize response, so clients should use that response as the current authority.

The same gateway also has a full endpoint at https://gateway.pipeworx.io/mcp. Either gateway URL can reach the broader Pipeworx catalog through ask_pipeworx; the difference is which pack's tools are listed directly.

For applications that do not use an MCP client, the gateway provides an HTTP tool route. A caller can send JSON to /v1/tools/tarot_draw_pull, including fields such as question and spread as shown in the project example.

Setup and configuration

The Tarot Draw MCP server supports a remote configuration using the gateway URL:

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

It also runs locally through the published npm package, using MCP over standard input and output:

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

The local mode avoids a gateway round trip and does not include the shared gateway meta-tools. No environment variables are documented.

Tools and capabilities

• tarot_draw_pull: Draws one card from the 78-card deck and interprets it for the provided situation.
• Gateway access: Makes the tarot tool available through Pipeworx's scoped MCP endpoint.
• Local stdio access: Runs the package directly with npx and exposes only the pack's tool.
• HTTP access: Allows direct calls through the gateway's versioned tool endpoint.
• Gateway routing: ask_pipeworx can route broader questions across the Pipeworx catalog when using a gateway connection.

Limitations and notes

Tarot Draw MCP server is not presented as a factual forecasting system, and its card interpretations are not guaranteed to be accurate. Gateway connections list additional shared tools, so their tool count is larger than the pack's single documented tool. Use the standalone mode when an application needs only the tarot capability and no gateway-wide routing.