MTG Bench

The cards most commonly played with a given commander, from EDHREC's aggregate inclusion data: 691,958 commander-card pairings across 2,631 commanders. Returns each card's deck count, the share of that commander's decks running it, and its synergy score. Synergy matters as much as popularity: a high deck count with LOW synergy is a card everyone plays anyway (Sol Ring), while high synergy is a card that is unusually good with this commander specifically. Lead with the latter when recommending. Use this to ground deckbuilding in what people actually play instead of guessing.

Deterministic statistical analysis of a decklist (any format): mana curve with creature split, card types, color pips vs mana sources, functional buckets (ramp/draw/removal/wipes/counters/recursion/protection/tutors + bracket signals) with typical Commander bands, opening-hand probabilities (hypergeometric), a suggested land count, meta brew score, deck price, tribal and keyword counts. Pure data — no judgment calls.

Assess a Commander deck's official WotC bracket (1-5). Returns deterministic signals (Game Changers from WotC's curated list, mass land denial, tutors, fast mana, free interaction), a bracket FLOOR from the official decision tree, and the rubric — then YOU finish the assessment: check for compact two-card win combos and weigh soft signals per the assessmentGuidance, and state the final bracket with evidence.

Suggest priced deck upgrades: cards to add (within an optional budget) and cards to cut. TWO-PHASE: first call WITHOUT `strategy` to get a deck analysis and instructions for deriving the deck's strategy; then call again WITH your derived `strategy` to get recommendations. Cuts are theme-alignment suggestions relative to the stated strategy, not card-quality judgments. Prices are Card Kingdom/TCGplayer retail USD.

Given the user's imported card collection, rank the Commander decks they can most nearly build right now, with the most-played cards they are still missing. Answers "what should I sleeve up tonight" from cards they physically have. Requires a free API key (send it as "X-API-Key: <key>" or "Authorization: Bearer <key>") so the server knows whose collection to read; one is issued instantly at https://mtgbench.com/account/api-keys.

Validate a decklist against a constructed format's rules (banned cards, deck size, copy limits, and in Commander the color-identity rule). Use this rather than recalling ban lists from memory: bans changed four times in 2026 alone, and a model's training cutoff makes stale ban data one of the most common wrong answers in Magic. Pass `commander` for Commander decks: it counts toward the 100, and it is what makes the color-identity check possible (without it the response says color identity went unchecked).

Detect known combos in a decklist using Commander Spellbook's curated database — combos fully present, plus near-misses one card away (with that card's price). Pass `format` (and `commander` for Commander) so near-miss suggestions are filtered to legal, in-color-identity adds. Use this instead of recalling combos from memory; also feeds rate_deck's compact-combo check.

Given one or more cards the user ALREADY has, find cards that work with them. Seeded by example rather than by description: pass the cards, get partners. Use semantic_card_search instead to describe a desired effect in words, and search_cards for structured filters. `limit` defaults to 10 and caps at 100 per call.

Fetch full detail for ONE card by exact name or id: oracle text, mana cost, type line, format legalities, and a brief summary of its printings. Use get_card_printings instead when the complete printing list matters (choosing a specific art, set, or finish).

Fetch a card's image. The returned image content block IS the display — the client renders it directly; do not build custom HTML/widgets around the imageUrl, since sandboxed widget environments block external image hosts. Optionally pick a specific printing (setCode) or size (small, normal, large, png, art_crop, border_crop, or WEBP: thumb, grid, display).

List EVERY printing of a card (set, rarity, artist, finish, collector number). get_card already returns a short printings summary, so reach for this only when the full list is the point.

Fetch the OFFICIAL Wizards rulings for one card, with their dates. These are Wizards' own answers to the corner cases players argue about. Use this for any "how does this card actually work" question, and quote the ruling rather than paraphrasing from memory — rulings are among the most frequently hallucinated things in Magic. Use search_rules instead for general mechanics not tied to a specific card.

Fetch a Comprehensive Rules entry and its lettered subrules by exact number (e.g. "601.2" returns 601.2 and 601.2a-i). Use after search_rules to read a rule's full context.

Summarize the user's imported collection: how many distinct cards, total copies, and where it was imported from. This is the SUMMARY only. Use search_my_collection to look up individual owned cards, and what_can_i_build to rank commanders they could assemble. Requires a free API key (send it as "X-API-Key: <key>" or "Authorization: Bearer <key>").

Check whether card names are REAL, in bulk. Returns exact / not_found per name, with the canonical spelling and id for the ones that exist. Call this reflexively before presenting any decklist or card recommendation you generated: the most common failure in Magic assistance is confidently naming cards that do not exist, or that exist with different text. Cheap, batched, and safe to call on every card you are about to mention. Accepts either a `names` array or a pasted `text` decklist.

Find cards by NAME or by structured filters (colors, color identity, types, mana value, format legality, sets). Use when the query can be expressed as filters: "red instants under 3 mana", "legendary artifacts in Standard", "cards named Bolt". Use semantic_card_search instead when the user describes an EFFECT rather than a filter ("cards that make a treasure when I attack"). Use find_synergies instead when they name cards they already have and want things that pair with them. Searches every Magic card; use search_my_collection to search only what the user owns. `limit` defaults to 25 and caps at 100 per call.

Search only the cards the user OWNS, by name, colors, or type. Set notInDecks to surface owned cards not currently used in any of their decks (the "what is sitting idle in my binder" question). Use search_cards instead to search every Magic card regardless of ownership. Returns at most 100 owned cards per call, with the full match count in `total`. Requires a free API key (send it as "X-API-Key: <key>" or "Authorization: Bearer <key>").

Semantic search over the Magic Comprehensive Rules, glossary, and 84k card-specific rulings. Use for any rules/interaction question; answer FROM the returned chunks and cite rule numbers (e.g. 601.2a). Filter kinds to ["ruling"] for card-specific questions or ["rule","glossary"] for general mechanics.

Vector search over card TEXT, for describing an effect that cannot be written as a filter: "cards that make a token when I attack", "punish opponents for drawing", "does what Rhystic Study does but cheaper". This is a query Scryfall syntax cannot express. Use search_cards instead for structured filters (color, type, mana value, set). Use find_synergies instead when the user names specific cards and wants partners for them. `limit` defaults to 10 and caps at 100 per call.