Skip to main content
Glama
JoeMoCode

Scryfall MCP Server

by JoeMoCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Scryfall MCP Server

No user-submitted related servers found.

    Related Servers

    • mystic-tutor-mcp

      Abbabon
      F
      license
      A
      quality
      D
      maintenance
      Provides AI assistants with real-time access to Magic: The Gathering card data, prices, rulings, search, and synergy discovery via the Scryfall API.
      5
      -

    • MTG Deck Manager MCP Servers

      artillect
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables Magic: The Gathering players to manage decks and access card information through Claude, supporting gameplay actions like drawing cards and mulligans while providing Scryfall API integration for card lookups.
      15
      -

    • Scryfall MCP Server

      KaminaDuck
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants with access to Magic: The Gathering card data via Scryfall API, enabling card search, image downloads, and database management.
      10 npm
      2
      Apache 2.0

    • MTG Card Lookup MCP Server

      jabelk
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables fuzzy lookup of Magic: The Gathering cards by name using the Scryfall API, returning card details including type, oracle text, mana value, and images.
      MIT

    • Scryfall MCP Server

      cryppadotta
      A
      license
      A
      quality
      D
      maintenance
      Enables interaction with the Scryfall API, allowing users to search for Magic: The Gathering card details, retrieve card rulings, and access pricing information using the Model Context Protocol.
      7
      42,316 npm
      34
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_card_details for exact card lookup, get_random_card for random cards, get_set_info for set metadata, and search_cards for flexible queries. No overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (get_card_details, get_random_card, get_set_info, search_cards). The use of 'get' and 'search' as verbs is uniform and predictable.

    Tool Count5/5

    With 4 tools, the server is well-scoped for a card database. The tools cover the primary needs: searching, getting details, random retrieval, and set information. This is an effective small set without bloat.

    Completeness4/5

    The core functionalities are covered: search, detail, random, and set info. Minor gaps like fetching by ID, rulings, or card art exist but do not break typical workflows. Agents can work around these.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources