MTG Cart Companion is live on the Chrome Web Store

DHSeaDev — Chrome Extensions, Windows Tools, & Idle Games

MTG Cart Companion has cleared review and is live on the Chrome Web Store. It turns any card name on any web page into a Magic deck list, then hands that list to a marketplace — right-click a name in a forum post, build the deck in the side panel, export in one step.

Get it on the Chrome Web Store · What it does · Privacy

What shipped

  • Right-click any card name on any page — forums, articles, video descriptions
  • Browse and pick printings by artwork rather than by spelling
  • Click any card to read its rules text at full size, without leaving the panel
  • Scan a whole page and import an entire decklist in one pass
  • Export to Mass Entry, Moxfield, Archidekt, Arena, plain text or CSV
  • Share a deck by link or file — the list rides in the URL fragment, so nothing is uploaded
  • Five mana-colour themes, each contrast-checked in light and dark

No account, no tracking, no server. Card data comes from Scryfall; that is the only host it contacts.

The shared-deck page is real now too

Share links used to 404 for anyone without the extension installed. The landing page exists now: paste a share link and it decodes the decklist in your browser and shows it. Nothing is uploaded to read it — the deck travels inside the part of the URL after the #, which browsers never transmit to a server, so the site never receives it and has no log of it.

A real 100-card Commander deck compresses to a fragment of about a thousand characters, measured before the feature was written rather than after.

What is still open

One honest gap. The page-scan feature was the hardest thing in this build to get right — it was structurally dead in an early version, requesting a permission it could never actually ask for. That is fixed and the permission path is verified. What is not verified by me is the moment a real person clicks Scan and Chrome shows the permission prompt: a headless browser cannot display that dialog, so the prompt itself was only ever exercised by hand.

Everything else — the deck store, the exporters, the share round-trip, the parser — is covered by 169 automated tests and a mutation campaign that deliberately breaks the code to check the tests can still fail.

Found a bug, or a card that will not resolve? Tell me.

Leave a Reply

Your email address will not be published. Required fields are marked *