get_card_by_id
Retrieve a card by its Scryfall ID (a 36-char UUID). Returns the card data in JSON.
LABSCO SUMMARY
Rulings and prices are addressed the same two ways as the card itself.
The symmetry is what makes it quick to use: whichever handle you already have — an ID out of a search result or an exact name off the card — there is a price tool that takes it, and the rulings tool accepts the Oracle ID as well as the Scryfall one. search_cards returning only the basic fields is a sensible default that keeps a broad search cheap and leaves the full record to the get tools. The get_card_by_name description adds one caveat: when several cards share an exact name, Scryfall returns one of them, usually the most relevant printing, rather than all of them.
What it is
A read-only Scryfall server covering card search, retrieval by ID or exact name, official rulings, prices, and a random card.
What you get
- search_cards by text query, including oracle-text searches, returning name, set, collector number and ID for each match
- Retrieval by Scryfall ID — a 36-character UUID — or by exact English name, returning the card JSON
- get_rulings, taking a Scryfall ID or an Oracle ID and returning the official rulings, each with a published_at date and a comment
- Prices addressed either by ID or by exact name, returning usd, usd_foil, eur and tix
- random_card, returning a random Magic card
Requirements
Nothing — no account, no key.
Setup effort
One command — npx scryfall-mcp-server
USE CASES
01
Settling a rules argument in the middle of a game
The card is fetched by its exact English name and the official rulings come back with the date each was published, which is what decides whether an interpretation still applies.
02
Finding every card that does the thing you are describing
Scryfall's own query language is passed through untouched, so an oracle-text search returns the matching cards with their sets and collector numbers, and a card can then be pulled in full by id.
03
Pricing a trade before you agree to it
Prices come back per card as usd, usd_foil, eur and tix, by name when you have one and by id when the name is ambiguous across printings.
04
Pulling a card at random for a prompt or a test fixture
One call returns a random card's data, which is a starting constraint for a deck idea or a fixture for something being built against the card schema.
7 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_card_by_name
Retrieve a card by its exact English name, e.g. 'Black Lotus'. Returns the card data in JSON. If multiple cards share that exact name, Scryfall returns one (usually the most relevant printing).
get_prices_by_id
Retrieve price information for a card by its Scryfall ID. Returns JSON with usd, usd_foil, eur, tix, etc.
get_prices_by_name
Retrieve price information for a card by its exact name. Returns JSON with usd, usd_foil, eur, tix, etc.
get_rulings
Retrieve official rulings for a specified card by Scryfall ID or Oracle ID. Returns an array of rulings. Each ruling has a 'published_at' date and a 'comment' field.
random_card
Retrieve a random Magic card from Scryfall. Returns JSON data for that random card.
search_cards
Search for MTG cards by a text query, e.g. 'oracle text includes: draw cards'. Returns a list of matching cards (with basic fields: name, set, collector_number, ID). If no matches are found, returns an error message from Scryfall.
BEFORE YOU INSTALL
What to know first
Tools you get
7 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 7 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"scryfall-mcp-server": {
"command": "npx",
"args": [
"scryfall-mcp-server"
]
}
}
}npx
TERMINAL
npx scryfall-mcp-server
