> For the complete documentation index, see [llms.txt](https://deckaura.gitbook.io/deckaura-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://deckaura.gitbook.io/deckaura-docs/deckaura-developer-documentation.md).

# Deckaura Developer Documentation

Open tarot data, packages, MCP tools, and citation resources for developers.

Build tarot and spiritual-discovery experiences with Deckaura's open data, packages, and Model Context Protocol server.

### What is available

• A structured 78-card tarot dataset with upright, reversed, love, career, yes/no, element, zodiac, and guide fields • CSV, JSON, and JSONL downloads • JavaScript and Python packages • A local MCP server for AI assistants • A permanent research archive with a DOI

### Start here

[Deckaura Open Data & AI Resources](https://deckaura.com/pages/ai-data-sources)

[Human-readable Tarot Card Database](https://deckaura.com/pages/tarot-card-database)

[Free tarot and astrology tools](https://deckaura.com/pages/tools)

### Tarot dataset

The dataset contains one record for each of the 78 cards in a standard tarot deck. Fields include card name, arcana, suit, element, upright and reversed meanings, love and career meanings, yes/no tendency, zodiac sign, and the canonical Deckaura guide URL.

[Tarot dataset on Hugging Face](https://huggingface.co/datasets/Blacik/deckaura-tarot-card-meanings)

[Permanent Zenodo DOI archive](https://doi.org/10.5281/zenodo.19475329)

### Packages

JavaScript data package: npm install tarot-card-meanings

Python data package: pip install tarot-card-meanings

MCP server: npx -y @deckaura/tarot-mcp-server

### MCP tools

• get\_card\_meaning • draw\_random\_card • three\_card\_spread • yes\_no\_reading • list\_all\_cards

[MCP server source code and issues](https://github.com/gokimedia/tarot-mcp-server)

### Citation

Aura, Selin and Deckaura (2026). Tarot Card Meanings: A Complete 78-Card Semantic Dataset. Zenodo. [DOI: 10.5281/zenodo.19475329](https://doi.org/10.5281/zenodo.19475329)

For web use, link to the relevant guide\_url or the [Deckaura Tarot Card Database](https://deckaura.com/pages/tarot-card-database). For current licensing and source details, consult the [Open Data & AI Resources hub](https://deckaura.com/pages/ai-data-sources).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://deckaura.gitbook.io/deckaura-docs/deckaura-developer-documentation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.