Documentation
How to use MTG Copilot, and how the system underneath it works.
MTG Copilot builds Commander decks with an AI that reasons over a grounded card database. These pages cover both halves of that: how to use the app, and how the system underneath it works. The second half is written for readers who want to check the machinery, which most of this site still is.
Where to start
| If you want to | Start at |
|---|---|
| use a feature of the app | Using the app |
| understand what a value means | Card data |
| look up a table or a column | Data model |
| write a query | Search |
| know what the AI is handed | AI |
| get your collection in, or out | Your data |
| know what runs on a schedule | Workflows |
| read all of this as an agent | llms.txt |
The two data sections answer different questions. Card data explains what a value means and how it got there. Data model is the generated column reference, one page per table, with the provenance of every field.
These docs describe the product, not the game
Magic's own vocabulary already lives in the app, with the citations attached:
the Comprehensive Rules at /search/rules, every game concept
with its official definition and rule references at
/search/concepts, and the semantic tag vocabulary at
/search/tags. All three are searchable.
So these pages define no Magic terminology. Where one leans on a game concept it links to the app's definition, which is the copy with the rule numbers attached. A second definition here would be a second thing to keep in sync.
The split decides where anything new belongs:
- The app explains the game. Rules, concepts, keywords, what a card does.
- The docs explain our product. How to use a feature, where a value came from, what refreshes it, how a query is executed, what the model was handed.
Reading the reference
Every field in the data model carries its provenance: the source it came from, the job that owns it, and how often that job runs. Those pages are generated from a typed registry, so a column documented here exists and a column that exists is documented here.
That covers card data. The tables holding your own decks and collection are listed in your data, with a reference page for each as it lands.
For agents
Every page is available as Markdown. Request any docs URL with
Accept: text/markdown to get the source, and /llms.txt indexes
the whole tree. The generated reference tables are expanded in that output, so a
fetched page carries the columns themselves.