draw_cardsLABSCO SUMMARY
The randomness comes from the server, not from the model.
Models are poor at picking at random, which is precisely what a spread depends on. This one draws from an actual deck of 78 and can hand back the card image, so the conversation is about interpreting the card rather than inventing it.
What it is
A Swift MCP server holding the traditional 78-card tarot deck. Draws use seeded random number generation rather than the model's own idea of chance, and cards can be returned as base64-encoded images.
What you get
- Anywhere from 1 to 78 cards drawn in a single request
- The full 78-card deck listed
- Card images returned base64-encoded, fetched by card URI
- Validation on the draw count, so bad input errors rather than passing silently
Requirements
A recent Swift toolchain on a recent macOS to build it; the Just command runner is optional. No account, no key.
Setup effort
One command — swift-tarot-MCP
USE CASES
01
Pulling a single card
One draw, from a deck the model did not choose from.
02
Laying out a multi-card spread
Draw the number of cards the spread calls for in one request, without repeats being fudged.
03
Seeing the card rather than reading its name
Draw, then fetch the image for the cards that came up.
04
Looking up what is in the deck
List all 78 cards, for checking a name or planning a spread.
3 tools
Listed in project docs. Your client may show a different list.
get_full_deckfetch_imagesBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
swift-tarot-MCP on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
swift-tarot-MCPMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"tarot": {
"command": "swift-tarot-MCP",
"args": []
}
}
}
