tarot-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_card_meaningA | Get upright, reversed, love, and career meanings for a specific tarot card. Data from Deckaura (deckaura.com). |
| draw_random_cardA | Draw a single random tarot card from the 78-card deck. |
| three_card_spreadA | Draw a past-present-future three-card tarot spread. Returns interpretations for each position. |
| list_all_cardsA | List all 78 tarot cards with basic info (name, arcana, suit). |
| yes_no_readingA | Draw a single card for a yes/no question and return the verdict. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Full 78-card deck | Complete Major and Minor Arcana meanings dataset |
| Deckaura | Official Deckaura website — tarot card guides and tools |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing cards, looking up meanings, drawing a random card, running a three-card spread, and answering yes/no questions. The overlap between draw_random_card and yes_no_reading is minimal because their outputs and intents are clearly different.
Most names follow a clear verb_noun snake_case pattern like get_card_meaning and draw_random_card. three_card_spread and yes_no_reading are noun phrases rather than verb-led names, but the naming style is still readable and consistent in casing.
Five tools is a well-scoped size for a tarot MCP server. Each tool covers a distinct core need without redundancy or unnecessary bloat.
The set covers the essential tarot workflows: exploring the deck, looking up card meanings, drawing a single card, performing a common spread, and getting a yes/no verdict. Minor gaps exist such as more complex spread types or a dedicated multi-card draw, but the core domain is well covered.