Tom Bombadil
CommanderA five-color Saga engine that snowballs value by chaining chapters into more Sagas, with Tom becoming very hard to answer once your lore count is online.
Public decks: 4Bracket: Varies
Card text
Legendary Creature — God Bard
As long as there are four or more lore counters among Sagas you control, Tom Bombadil has hexproof and indestructible.
Whenever the final chapter ability of a Saga you control resolves, reveal cards from the top of your library until you reveal a Saga card. Put that card onto the battlefield and the rest on the bottom of your library in a random order. This ability triggers only once each turn.
Building around this commander?
Use MTG Master to build or analyze a Commander deck around this card, check consistency, and find weak spots before your next game.
Overview
- Plays like an enchantment-based value deck: deploy Sagas, let them advance, then convert finished chapters into more board presence.
- Tom Bombadil rewards pacing your Saga completions so you can trigger the once-per-turn chain as often as possible across a full round.
- Often prioritizes mana fixing early to reliably cast multicolor Sagas and your commander on time.
- Once you control enough total lore counters, Tom tends to function as a resilient engine piece (hexproof/indestructible) rather than a win condition by himself.
- Games usually close by overwhelming the table with repeated Saga payoffs, removal chapters, and accumulated board advantage.
Common lines
- Spend early turns fixing mana, then land Tom and start sequencing Sagas so at least one final chapter resolves on each turn cycle when possible.
- Use Saga chapters to answer threats and stabilize, then let the chain trigger replace each finished Saga with another one from the library.
- If your lore count dips below four after a Saga leaves, you may need to rebuild with additional Sagas before Tom is safe again.
- Lean on broad interaction and reset buttons when the table gets ahead, then rebuild quickly by continuing to hit Sagas off the chain trigger.
Strengths
- Long-game inevitability: repeated Saga completions can keep your board and answers flowing.
- Resilient commander once online, making it easier to keep your engine intact through removal-heavy tables.
- Flexible gameplay: Sagas naturally cover removal, tokens, recursion, and value depending on what you flip into.
- Good at grinding through midrange boards by turning each “end” into another permanent.
Weaknesses
- Setup dependent: without enough Sagas/lore counters, Tom is easier to interact with and your engine can sputter.
- Can be slower to close; value chains may dominate resources without ending the game quickly.
- Vulnerable to enchantment hate and exile-based interaction that clears Sagas efficiently.
- Revealing until a Saga can take time and may lead to long turns if you’re not practiced with your sequencing.
Rule zero notes
- Call out whether you’re aiming for a slow value chain or a faster, more deterministic endgame.
- Let the table know if you run frequent board wipes (for example, Fumigate) to reset and rebuild.
- Mention that Tom’s trigger involves repeated revealing and can add table time; be ready to play it briskly.
- Clarify how interactive your Saga suite is (more removal chapters vs more goldfishing/value).
- If you include recursion loops or lock-style play patterns, disclose them up front (not implied by the commander alone).
Matchups
Best into
- Creature-heavy midrange pods where repeated removal chapters and board development matter.
- Games that go long and reward incremental value and resilience.
- Tables light on enchantment removal or exile-based answers.
Struggles against
- Fast combo pods where a slower engine struggles to interact early and often enough.
- Decks that heavily pressure enchantments (mass enchantment removal, repeated exile effects).
- Strategies that punish high-cost, multicolor setups by attacking mana and tempo.
Recent public decks
Staples
Browse all public decksFAQ
How does Tom Bombadil actually win games?
Typically by accumulating enough Saga payoffs that you out-resource the table, then converting that advantage into lethal combat or overwhelming board control.
Do I want multiple Sagas to finish on the same turn?
Not usually, since Tom’s chain trigger only happens once per turn; you often prefer one final chapter per turn cycle if you can plan for it.
What happens if I reveal a lot of cards and don’t hit a Saga quickly?
You keep revealing until you find a Saga, then the rest go to the bottom in a random order; it’s powerful but can be time-consuming, so practice helps.
How important is mana fixing in five colors here?
Very; you want to cast multicolor Sagas and your commander reliably, so rocks and fixers (for example, Arcane Signet or Chromatic Lantern) often matter a lot.
Is Tom safe once he has hexproof and indestructible?
He’s much harder to answer, but not invulnerable; board wipes that exile or force sacrifice and effects that remove your Sagas can still break up the engine.