Search Guide

Use search to find commander decks by commander, color identity, cards, tags, oracle text, printings, dates, and built-in filters.

You can keep it simple and type something like atraxa, or build a more specific search like cm:atraxa card:"Sol Ring" is:legal.

Start Here

  • Type a commander name to search commanders: atraxa
  • Put filters next to each other to narrow results: atraxa tag:blink
  • Use OR when either option should match: cm:atraxa OR cm:voja
  • Put - in front to exclude something: -tag:budget
  • Use parentheses when you want to group part of the query: (cm:atraxa OR cm:voja) is:legal
  • Sort the results with order: and dir:: order:name dir:asc

Search Basics

  • Bare words search commander names. atraxa works like commander:atraxa.
  • Putting clauses next to each other means AND.
  • AND and OR are case-insensitive, but they must be separate words.
  • Negation uses -, not NOT.
  • Use double quotes for values with spaces, such as card:"Sol Ring".
  • Field names are case-insensitive.
  • Parentheses control order of operations.
  • Search order is: parentheses, then negation, then AND, then OR.
  • Unknown fields and unknown card names return an error instead of being silently ignored.

Commander vs Deck Filters

Every field matches at one of two levels, and the field cards below are tagged with which one:

  • Commander filters match a property of the commander itself — its name, color identity, oracle text, and the sets it appears in. They decide which commanders show up.
  • Deck filters look inside the individual decks built for a commander — the cards they run, their tags, and when they were last updated. A commander matches when at least one of its decks matches, and results reflect how many of its decks qualify.

You can freely combine both. cm:atraxa card:"Sol Ring" keeps commanders named Atraxa (a commander filter) whose decks actually run Sol Ring (a deck filter).

Supported Fields

commandercmcmdrCommander

Search by commander name.

Operators
: contains text · = exact name
Examples
cm:atraxacommander=“Atraxa, Praetors’ Voice”
ciCommander

Filter by color identity.

Operators
: or <= subset · >= superset · = exact match
Examples
ci:wuci>=wuci=wubrg
oracleoCommander

Match the commander’s rules text (and name).

Operators
: contains text · /regex/ regular expression
Examples
o:flyingoracle:“draw a card”o:/deals? damage/
setsCommander

Match the set a commander was printed in.

Operators
: printed in set · = only from set
Examples
set:mh3s:cmmset=lea
releasedrelCommander

Filter by a commander’s set release date.

Operators
: = > >= < <= against a yyyy-MM-dd date
Examples
released>=2024-01-01rel<2015-01-01
isCommander

Apply a built-in filter.

Operators
:
Examples
is:legalis:partneris:new
cardccnDeck

Find decks that contain a card.

Operators
: · = · !=
Examples
card:“Sol Ring”-card:“Mana Crypt”
tagtDeck

Match a deck tag.

Operators
: · =
Examples
tag:blink-tag:budget
updatedupDeck

Filter decks by when they were last updated.

Operators
: = > >= < <= against a yyyy-MM-dd date
Examples
updated>=2025-01-01up<2024-06-01
includeModifier

Widen results to nonstandard commanders.

Operators
:
Examples
include:extras
orderModifier

Sort the results by a field.

Operators
:
Examples
order:nameorder:releasedorder:color
dirModifier

Choose ascending or descending order.

Operators
:
Examples
dir:ascdir:desc

Search by Commander

Commander filter.
  • Bare text searches commander names with a case-insensitive contains match.
  • commander: works the same way.
  • commander= does a case-insensitive exact match.
  • commander!=... is not supported. Use -commander:... instead.
  • Aliases: cm, cmdr.

Examples:

  • atraxa
  • commander:"Atraxa, Praetors' Voice"
  • commander="Atraxa, Praetors' Voice"
  • -cm:atraxa

Search by Color Identity

Commander filter.

Use the letters W, U, B, R, and G.

  • ci:wu means the deck’s color identity is a subset of white-blue.
  • ci<=wu means the same thing as ci:wu.
  • ci>=wu means the deck includes both white and blue.
  • ci=wu means the deck is exactly white-blue.
  • Only :, <=, >=, and = are supported. A bare > or < is not.

Examples:

  • ci:w
  • ci:wu
  • ci>=br
  • ci=wubrg

Search by Oracle Text

Commander filter.

oracle: searches the commander’s combined rules text and card name.

  • oracle: and oracle= both do a case-insensitive contains match.
  • Wrap a value in /…/ to match a case-insensitive regular expression instead.
  • A quoted value like oracle:"/x/" stays a literal substring rather than a pattern.
  • Alias: o.

Examples:

  • o:flying
  • oracle:"whenever this creature attacks"
  • o:/draw (a|two) cards?/
  • -o:trample

Search by Set

Commander filter.

set: matches commanders whose card was originally printed in a given set, using Scryfall set codes.

  • Set codes are case-insensitive, so set:MH3 matches mh3.
  • set: matches when any of the commander’s cards came from that set.
  • set= is an exact match: the commander’s only original printing is that set. This mostly matters for single-card commanders and rarely matches partners.
  • An unknown set code matches nothing rather than erroring.
  • Alias: s.

Examples:

  • set:mh3
  • s:cmm
  • set=lea

Search by Release Date

Commander filter.

released: filters commanders by the release date of the set their card comes from. Dates are yyyy-MM-dd.

  • released: and released= mean that exact release day.
  • >, >=, <, and <= compare against the date.
  • A commander matches when any of its original sets satisfies the comparison.
  • Sets without a known release date never match.
  • Alias: rel.

Examples:

  • released:2023-11-17
  • released>=2024-01-01
  • rel<2015-01-01
  • ci:wu rel>=2022-01-01

Built-In Filters

Commander filter.

Supported is: values:

ValueMeaning
legalThe commander is legal in the format.
partnerThe deck uses multiple commanders.
newThe commander appears in one of the ten most recently released sets.

Examples:

  • is:legal
  • is:partner
  • is:new
  • cm:tymna is:partner

Search by Card

Deck filter.
  • Card searches use exact card names, not partial text.
  • Matching is case-insensitive.
  • Multi-word card names must be quoted.
  • If a card name cannot be resolved, the query returns an error.
  • card: and card= match decks that run the card; card!= matches decks that do not.
  • Aliases: c, cn.

Examples:

  • card:"Sol Ring"
  • c:"Smothering Tithe"
  • cn!="Mana Crypt"
  • card:"Sol Ring" OR card:"Arcane Signet"

Search by Tag

Deck filter.
  • Tag matching is exact, not partial.
  • tag: and tag= behave the same way.
  • tag!=... is not supported. Use -tag:... instead.
  • Alias: t.

Examples:

  • tag:blink
  • t:sacrifice
  • -tag:budget

Search by Last Updated

Deck filter.

updated: filters decks by the day they were last changed. Dates are yyyy-MM-dd.

  • updated: and updated= mean that exact day.
  • >, >=, <, and <= compare against the date.
  • Stored dates are truncated to the day, so up>2024-01-01 means “updated on 2024-01-02 or later”.
  • Because it inspects individual decks, this is a deck filter — a commander matches when one of its decks qualifies.
  • Alias: up.

Examples:

  • updated>=2025-01-01
  • up<2024-06-01
  • cm:atraxa up>=2025-01-01

Including Extras

Result modifier.

By default, searches only return standard commanders. Use include:extras to widen the results to nonstandard commanders as well, such as:

  • Planeswalkers used as commanders.
  • Nonlegendary creatures used as commanders.
  • Illegal partner combinations.

include:extras shows these alongside the standard results. It combines with any other filters, so you can scope the extras just like a normal search.

Examples:

  • include:extras
  • ci:ur include:extras
  • cm:"Jodah, the Unifier" include:extras

Ordering Results

Result modifier.

Use order: to sort the results and dir: to choose the direction. Both apply to the whole search, so keep them at the top level — they only take effect outside OR, -, and parentheses.

Supported order: values:

ValueSorts byAliases
popularityHow many decks use the commander (the default).pop, decks
nameCommander name, alphabetically.
releasedSet release date.release, date
colorColor identity.colour, ci

Supported dir: values:

ValueMeaningAliases
ascAscending.ascending
descDescending.descending
  • Leave order: off to sort by popularity.
  • Leave dir: off to use each field’s natural direction.
  • order: and dir: values are case-insensitive.

Examples:

  • order:name
  • order:released dir:desc
  • cm:atraxa order:color
  • is:legal order:name dir:asc

Putting It Together

Examples:

  • cm:atraxa is:legal
  • cm:atraxa ci>=wubg
  • card:"Sol Ring" -tag:budget
  • (cm:atraxa OR cm:voja) is:partner
  • o:flying ci:wu set:mh3
  • is:new released>=2024-01-01 up>=2025-01-01
  • ci:wu is:legal order:name dir:asc

Quoting Tips

  • Use double quotes for anything with spaces.
  • Quoted text is treated as one value.
  • Bare words are split on whitespace.
  • Escape quotes and regular expression slashes by preceding them with a backslash.

Examples:

  • "Sol Ring"
  • card:"The One Ring"
  • commander:"Atraxa, Praetors' Voice"
  • cm:"Henzie \"Toolbox\" Torre"

Common Mistakes

  • NOT tag:budget: use -tag:budget instead.
  • card:sol: card searches need an exact card name such as card:"Sol Ring".
  • tag:bud: tag search is exact, not partial.
  • commander!=atraxa: use -commander:atraxa instead.
  • ci>wu: use ci>=wu, ci<=wu, ci:wu, or ci=wu.
  • released:2024: dates must be full yyyy-MM-dd, such as released:2024-01-01.
  • set:"Modern Horizons 3": use the set code, such as set:mh3.
  • (cm:atraxa order:name): keep order: and dir: at the top level, not inside OR, -, or parentheses.