Skip to main content
Glama
matthewdtowles

iwantmymtg-mcp

by matthewdtowles
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to iwantmymtg-mcp

  • 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

  • MTG-MCP

    wtfregia
    A
    license
    Not graded
    quality
    C
    maintenance
    A comprehensive Model Context Protocol server that provides AI assistants with rich Magic: The Gathering information, including card data, comprehensive rules, EDHREC recommendations, combo interactions, and intelligent Commander deck generation.
    1
    MIT

Related Servers

  • Scryfall MCP Server

    andreapede
    A
    license
    Not graded
    quality
    D
    maintenance
    MCP server for searching and retrieving Magic: The Gathering card information via the Scryfall API, with support for field presets, multiple output formats, and automatic rate limiting.
    42,316 npm
    MIT

  • mcp-scryfall

    haksanlulz
    A
    license
    Not graded
    quality
    A
    maintenance
    MCP server for live Magic: The Gathering card lookup via the Scryfall API. Grounds card references against live Scryfall data, with tools for exact, fuzzy, and search queries.
    8 npm
    MIT

  • Mystic Forge

    Kautiontape
    A
    license
    Not graded
    quality
    B
    maintenance
    Unified MCP server for Magic: The Gathering, combining Scryfall card search and pricing, EDHRec commander recommendations, Archidekt deck reading, and decklist validation into a single service.
    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 60 tools

Disambiguation4/5

Each tool generally targets a distinct resource+action, with descriptions that clarify boundaries (e.g., get_card_printings vs search_cards). However, the cluster of get_card, get_card_prices, get_card_price_history, and get_card_buylist have similar names and some overlapping data (get_card already includes prices), requiring careful reading.

Naming Consistency4/5

The set is mostly consistent snake_case verb_noun (list_, get_, add_, update_, create_, import_, export_). Deviations include mixing remove_ and delete_ for the same operation type (remove_inventory vs delete_deck), and using add/set/record/create for write actions across resources.

Tool Count2/5

60 tools is very high and well beyond the 25+ threshold for 'too many'. While the domain is broad, covering pricing, inventory, buy lists, decks, transactions, portfolio analytics, alerts, and notifications, the sheer count will strain context windows and increase selection difficulty, and some tools could be consolidated.

Completeness5/5

The tool surface provides full CRUD/lifecycle coverage for inventory, buy list, transactions, decks, price alerts, and notifications, plus robust card/set pricing and portfolio analytics. There are no obvious dead ends or missing core operations for the domain.

Maintenance

ActivitySlowing
ResponsivenessWithin a week

Resources