Swift Tarot MCP Server

Most developer tooling work still happens through a UI a human drives. Swift Tarot MCP MCP server moves it into the conversation instead. A Model Context Protocol (MCP) server that provides tarot card reading functionality. This server allows AI assistants to draw tarot cards, perform multi-card readings, and access the complete tarot deck.

The short version

• Flexible Card Drawing — Draw anywhere from 1 to 78 tarot cards in a single request
• Full Deck Access — View all 78 cards in the traditional tarot deck
• Card Images — Fetch base64-encoded images for tarot cards
• Deterministic Testing — Uses seeded random number generation for consistent testing
• Comprehensive Validation — Input validation with proper error handling

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

The tools it exposes

The server publishes 5 tools. What each one is for:

• Prerequisites — The Prerequisites tool exposed by this server
• draw_cards — The draw_cards tool exposed by this server
• get_full_deck — The get_full_deck tool exposed by this server
• fetch_images — The fetch_images tool exposed by this server
• Testing — The Testing tool exposed by this server

What it needs from you

• Swift 5.9 or later - macOS 13.0 or later - Just command runner (optional but recommended)

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Swift Tarot MCP's toolset — Prerequisites, draw_cards, get_full_deck and 2 more — is a fair guide to whether it matches your workflow. It is maintained by junebash; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.