mcp-scryfall
Related Servers
Alternatives to mcp-scryfall
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that searches and retrieves Magic: The Gathering card data from the Scryfall API.73,727 npmMIT
- AlicenseAqualityCmaintenanceMagic: The Gathering MCP server with card search, rules lookup, deck analysis, and Commander intelligence14112 npm4MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for searching and retrieving Magic: The Gathering card information via the Scryfall API, with support for field presets, multiple output formats, and automatic rate limiting.73,727 npmMIT
- AlicenseNot gradedqualityBmaintenanceUnified MCP server for Magic: The Gathering, combining Scryfall card search and pricing, EDHRec commander recommendations, Archidekt deck reading, and decklist validation into a single service.MIT
- FlicenseAqualityDmaintenanceMCP server for Magic: The Gathering Commander that provides card data from Scryfall and deckbuilding recommendations from EDHREC.5-
- AlicenseNot gradedqualityBmaintenanceMCP server for searching Flesh and Blood TCG cards, retrieving print variations, and browsing product catalogs via the CardVault API.MIT
TDQS
Scored across 7 tools
Each tool targets a distinct lookup mode: exact name, fuzzy name, query search, batch collection, random, rulings, and bulk data. Even the two name-based lookups are clearly separated by exact vs. fuzzy intent, and the descriptions explicitly call out when to use which.
Six of seven tools follow a consistent 'card_' prefix and snake_case naming (card_named, card_fuzzy, card_search, card_collection, card_random, card_rulings). The outlier 'bulk_default' breaks the prefix pattern, but it's still readable and the rest form a clear family.
Seven tools is well-scoped for a card-database server: single-card lookups, search, batch, random, rulings, and bulk data. Each tool earns its place with a distinct function, and the count is neither thin nor overwhelming.
Core card access is fully covered: exact/fuzzy lookup, query search, batch decklist resolution, rulings, random, and bulk corpus download. Minor gaps exist (e.g., no direct set/expansion list or card-by-ID endpoint), but these are workarounds via card_collection or card_search, and the typical Scryfall workflows are complete.