Scryfall MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Node environment (development or production) | development |
| LOG_LEVEL | No | Logging level (trace, debug, info, warn, error, fatal) | info |
| RATE_LIMIT_MS | No | Minimum milliseconds between API requests | 100 |
| HEALTHCHECK_DEEP | No | Enable deep health checks | false |
| SCRYFALL_TIMEOUT_MS | No | Timeout for Scryfall API requests in milliseconds | 15000 |
| SCRYFALL_USER_AGENT | No | User agent string for Scryfall API requests | ScryfallMCPServer/1.0 |
| RATE_LIMIT_QUEUE_MAX | No | Maximum size of the rate limiter queue | 500 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_cardsA | Search for Magic: The Gathering cards using Scryfall search syntax. Supports complex queries with operators like color:, type:, set:, etc. |
| get_cardB | Get detailed information about a specific Magic: The Gathering card by name, set code+number, or Scryfall ID |
| get_card_pricesB | Get current price information for a Magic: The Gathering card by name, set/number, or Scryfall ID |
| random_cardB | Get a random Magic: The Gathering card, optionally filtered by format or search criteria |
| search_setsC | Search for Magic: The Gathering sets with optional filtering by name, type, and release dates |
| query_rulesC | Search Magic: The Gathering comprehensive rules for specific interactions and rule clarifications |
| search_format_staplesC | Find format staples, meta cards, and role-specific cards for competitive play |
| search_alternativesB | Find budget alternatives, upgrades, or functionally similar cards |
| find_synergistic_cardsC | Find cards that synergize with a specific card, theme, or archetype |
| batch_card_analysisC | Analyze multiple cards for legality, prices, synergies, or deck composition |
| validate_brawl_commanderB | Validate if a card can be a legal commander in Brawl or Standard Brawl formats |
| build_scryfall_queryB | Convert natural language requests into optimized Scryfall search queries with explanations and alternatives |
| analyze_deck_compositionC | Analyze deck composition, mana curve, card types, and provide balance recommendations |
| suggest_mana_baseC | Suggest optimal mana base composition and land recommendations for a deck |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_card | Generate a comprehensive analysis of a Magic: The Gathering card including competitive viability, format positioning, synergies, and deck building suggestions |
| build_deck | Generate a deck building guide centered around a specific Magic: The Gathering card, including strategy, supporting cards, manabase, and sideboard suggestions |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Card Database | Complete Scryfall bulk card database with daily updates |
| Set Database | Complete Magic: The Gathering sets database with metadata and icons |
TDQS
Scored across 14 tools
Every tool has a clearly distinct purpose with no significant overlap. For example, get_card retrieves a single card, search_cards handles complex queries, and analyze_deck_composition focuses on deck analysis, making misselection unlikely.
All tool names follow a consistent verb_noun pattern using snake_case, such as get_card, search_cards, and analyze_deck_composition. This predictability aids in agent understanding and usage.
With 14 tools, the server is well-scoped for Magic: The Gathering card and deck management. Each tool serves a specific function, from card retrieval to deck analysis, without feeling excessive or insufficient.
The tool surface comprehensively covers the domain, including card search, price checks, deck analysis, rules queries, and format validation. There are no obvious gaps, supporting full agent workflows for MTG-related tasks.