sbwsz-mcp
Related Servers
Alternatives to sbwsz-mcp
- MIT
Related Servers
- AlicenseAqualityBmaintenanceProvides AI assistants with comprehensive Magic: The Gathering data including card info, combos, draft analytics, Commander metagame, constructed formats, sideboard strategy, deck building, and rules.74MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to search and retrieve Magic: The Gathering card data through the Scryfall API. Supports card searches, random card generation, autocomplete, set listings, and rulings lookup.221MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with access to Magic: The Gathering card data via Scryfall API, enabling card search, image downloads, and database management.102Apache 2.0
- AlicenseAqualityDmaintenanceProvides AI assistants with 69 tools, 19 prompts, and 21 resources for deep access to Magic: The Gathering, including card data, combos, draft analytics, Commander metagame, competitive constructed, sideboard strategy, deck building, and rules engine, working with any MCP client.5620MIT
- FlicenseNot gradedqualityAmaintenanceProvides Magic: The Gathering card, deck, provider, and statistical evidence tools for LLMs to make informed deckbuilding decisions.-
- FlicenseAqualityBmaintenanceEnables natural language querying of your Magic: The Gathering Arena collection, including owned cards, missing cards, deck building, and collection analysis via MCP.11-
TDQS
Scored across 6 tools
Most tools have distinct purposes: get_card_by_set_and_number retrieves a specific card, get_set and get_set_cards handle series data, get_sets lists all series, and search_cards performs general searches. However, get_set_cards and search_cards could be confused as both retrieve card lists, though their scopes differ (series-specific vs. general).
Tools follow a consistent verb_noun pattern (e.g., get_card_by_set_and_number, get_set, get_set_cards, get_sets, search_cards), which is clear and predictable. The exception is 'hzls', which uses an acronym and lacks a verb, slightly deviating from the pattern but not severely impacting readability.
With 6 tools, the server is well-scoped for Magic: The Gathering card data management. Each tool serves a specific function (e.g., retrieving cards, series, or generating images), and there are no redundant or missing tools for the apparent domain, making the count appropriate.
The tool surface covers core operations for MTG data: retrieving cards (by ID, series, or search), series information, and a creative image tool. Minor gaps exist, such as no explicit update or delete tools for data modification, but this is reasonable for a read-focused API, and agents can work around it with the provided search and retrieval functions.