Skip to main content
Glama

hearthstone-oracle

Hearthstone 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.

Features

  • Complete card database from HearthstoneJSON — every collectible card, auto-updated

  • Deck decoding and analysis — paste a deck code, get full card list, mana curve, and archetype breakdown

  • Strategy knowledge — archetypes, class identities, matchup dynamics, and game concepts

  • 9 MCP tools — search, lookup, decode, analyze, coach

Related MCP server: lorcana-oracle

Quick Start

claude mcp add hearthstone-oracle -- npx -y hearthstone-oracle

Card data is downloaded automatically from HearthstoneJSON on first run and stored locally in ~/.hearthstone-oracle/. No API key required.

Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "hearthstone-oracle": {
      "command": "npx",
      "args": ["-y", "hearthstone-oracle"]
    }
  }
}

Tools

Tool

Description

search_cards

Search cards by name, text, class, cost, type, rarity, set, or keyword

get_card

Get complete details for a specific card with fuzzy matching

get_keyword

Look up keyword/mechanic definitions with related cards

decode_deck

Decode a deck code into full card list with mana curve

analyze_deck

Analyze a deck's archetype, gameplan, strengths, and matchup profile

get_archetype

Learn about deck archetypes (aggro, control, combo, midrange, tempo, value)

get_class_identity

Strategic identity of each Hearthstone class

get_matchup

Theoretical matchup dynamics between archetypes

explain_concept

Fundamental game concepts explained for Hearthstone

How It Works

Two-layer architecture:

  1. Card data layer — Full card database from HearthstoneJSON, stored in a local SQLite database with FTS5 full-text search. Cards are fetched on first run and updated when newer game builds are available.

  2. Strategy layer — Built-in strategy knowledge covering archetypes, class identities, matchup theory, and core game concepts. Enables the server to provide coaching and analysis, not just raw card data.

Data Source

Card data provided by HearthstoneJSON by HearthSim. Auto-extracted from game files. Unrestricted use.

License

MIT

Available Tools

9 tools
analyze_deckA

Analyze a Hearthstone deck code to classify its archetype, explain its gameplan, identify strengths and weaknesses, and predict matchup dynamics. Use this for strategic deck coaching — it combines card data with strategy knowledge.

Inputs: deck_code (required).

decode_deckA

Decode a Hearthstone deck code into its full card list with mana curve and card type breakdown. Use this when a user shares a deck code and wants to see what's in it.

Inputs: deck_code (required).

explain_conceptA

Explain a fundamental Hearthstone game concept like card advantage, tempo, value, board control, or mana curve. Includes how the concept applies specifically to Hearthstone.

Inputs: name (required).

get_archetypeA

Get a detailed explanation of a Hearthstone deck archetype (aggro, control, combo, midrange, tempo, value). Includes gameplan, win conditions, strengths, weaknesses, and example decks. Use this when explaining deck building strategy.

Inputs: name (required).

get_cardA

Get complete details for a specific Hearthstone card including stats, text, keywords, and type. Use this when you know the card name (or close to it) and need full information. Supports fuzzy matching.

Inputs: name (required).

get_class_identityA

Get the strategic identity of a Hearthstone class — hero power implications, historical archetypes, strengths, weaknesses, and how the class approaches each game phase. Omit the class name to get an overview of all 11 classes.

Inputs: class_name.

get_keywordA

Look up a Hearthstone keyword or mechanic (e.g., Battlecry, Deathrattle, Discover) and see all cards that have it. Use this to explain what a keyword does or find all cards with a specific mechanic.

Inputs: name (required), player_class.

get_matchupA

Get the theoretical matchup dynamics between two Hearthstone archetypes. Explains who is favoured, why, the key strategic tension, and what each side should prioritise.

Inputs: archetype_a (required), archetype_b (required).

search_cardsA

Search for Hearthstone cards by name, text, class, mana cost, type, rarity, set, or keyword. Use this when you need to find cards matching specific criteria. Returns a summary list — use get_card for full details on a specific card.

Inputs: query, player_class, mana_cost, cost_op, +7 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of Hearthstone knowledge: deck analysis vs decoding, card search vs details, archetype vs concept vs matchup, class identity vs keyword. No overlapping purposes.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern (e.g., analyze_deck, get_card, search_cards). No mixing of conventions or vague verbs.

    Tool Count5/5

    9 tools cover a comprehensive yet focused set of Hearthstone oracle functions. The count is well-scoped for the domain—neither too sparse nor too heavy.

    Completeness5/5

    The tool surface covers card details, deck decoding and analysis, concepts, archetypes, matchups, keywords, and class identities. No obvious gaps for a knowledge-oriented Hearthstone assistant.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers