A
licenseA
qualityC
maintenanceHearthstone MCP server with card search, deck analysis, and strategy coaching. Gives LLMs access to every Hearthstone card plus built-in strategy knowledge for deck building and gameplay advice.
9
27 npm
2
MIT
hearthstone-decks-mcp
by YinshawnRao
Related Servers
Alternatives to hearthstone-decks-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server for Yu-Gi-Oh! card data, providing cards, prices, banlists, rules, rulings, relations, and deck tools via a local SQLite database with semantic search.-
- 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
- AlicenseAqualityAmaintenanceAn MCP server for searching and aggregating Disney Lorcana cards, enabling card lookup, deck building, and statistical analysis.1033 PyPI1MIT
- AlicenseNot gradedqualityCmaintenanceA comprehensive Model Context Protocol server that provides AI assistants with rich Magic: The Gathering information, including card data, comprehensive rules, EDHREC recommendations, combo interactions, and intelligent Commander deck generation.36 PyPI1MIT
- AlicenseAqualityBmaintenanceA comprehensive Model Context Protocol server that integrates with the Scryfall API to provide Magic: The Gathering card data to AI assistants like Claude.14112 npm1MIT
TDQS
B3.2/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: get_card_info retrieves details for a specific card ID, parse_deck_code processes deck codes to return deck information, and search_cards searches by card name. There is no overlap in functionality, making it easy for an agent to select the correct tool without confusion.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern (get_card_info, parse_deck_code, search_cards), using snake_case throughout. This predictability enhances readability and usability for agents, with no deviations in naming style.
Tool Count3/5
With only 3 tools, the server feels thin for a domain like Hearthstone decks, which might involve more operations such as creating, updating, or managing decks. While the tools cover basic retrieval and parsing, the count is borderline for the apparent scope, potentially limiting agent capabilities.
Completeness2/5
The tool set is significantly incomplete for a Hearthstone deck management domain. It lacks essential CRUD operations like creating, updating, or deleting decks, and does not cover lifecycle aspects such as deck validation or sharing. Agents will face dead ends when trying to perform common deck-related tasks beyond basic lookup and parsing.
Maintenance
ActivityInactive
ResponsivenessNo issues