Your decks, in your assistant
Build a Commander deck, improve one you own, or understand a tricky interaction. Connect your assistant to the same decks, collection and research tools Yama uses.
Yama hosts the MCP server. You connect to it with your own account; there is no separate Magic MCP package or card database to install. Yama is free. Your assistant's own plan and usage terms still apply.
Work from your theme, budget, declared bracket and protected cards. Get exact additions and cuts, compare the lists, check Commander legality, and stage a new deck or a replacement for review. Saved versions keep the previous list.
Search with full Scryfall syntax, inspect printings and rulings, explore EDHREC recommendations and Commander Spellbook combos, and look up current official rules with their source and effective edition.
Keep current and bracket alternatives, explained rough power, executable combos, exact swaps and dated local shopping evidence together in your private Research section. Preferred builds, swap answers and notes survive refreshed research.
Check quantities, proxies and locations; find cards outside deck boxes; estimate needed copies and dated singles costs. Propose collection additions, moves and condition updates.
Read public Moxfield and Archidekt decks, compare saved or proposed lists, sample reproducible opening hands, calculate source-draw probabilities and run bounded land-sequencing checks.
Read stock, current and planned lists, review swaps and propose ideas. Record your review answers, bought cards and installed swaps, including putting planned prints into the linked deck.
Read precon benchmarks, dated editorial upgradeability assessments, your lab runs, live progress and individual games. When you request it, stage a Phase or Forge experiment, more games, a repeat or a cancellation. Lab allowances and queue limits apply.
Recommendations are suggestions grounded in the available data. Community popularity does not prove a win-rate improvement. Mana checks state their assumptions; the land-sequencing model omits ramp, fetches, filters and mulligans. Missing prices stay unknown, and market prices are not store quotes or resale offers.
First sign in to Yama with a verified Google account. Use that account when the connection opens Yama's approval page. Reading this guide does not require an account.
The hosted server address is:
https://yama.ing/mcpThis is a tool endpoint, not a page to open in a browser.
claude mcp add --transport http --scope user yama https://yama.ing/mcp/mcp, select yama and choose Authenticate./mcp.Already have a Yama connection? Reuse it. See the official Claude Code MCP instructions for client installation, scopes and connection management.
https://yama.ing/mcp as the remote server URL.Your Claude plan or organization may control which connectors you can add. Follow the official Claude connector guide if the menus differ.
codex mcp add yama --url https://yama.ing/mcpcodex mcp login yamacodex mcp list to check the registration, and use /mcp inside Codex to inspect the active connection.See the official OpenAI documentation for MCP for Codex settings and other supported surfaces.
Use a client that supports Streamable HTTP and OAuth with the same server URL. If it cannot sign in, create an MCP-scoped key under Decks → Plans → Settings and follow the connection instructions shown there. Treat the key as a password. A plan-sync key cannot access MCP tools.
Inside Yama: Ask Claude already uses these tools when available for your account. No external connection is needed. Availability and allowance are shown in Yama.
Use the name of a deck in your account, or paste a list. Explain your playgroup goals and anything you want to keep.
Review my Aragorn deck with a $50 upgrade budget. Prefer cards I own, keep the monarch theme and avoid infinite combos. Show exact additions, cuts, estimated costs and tradeoffs before staging changes.
Build a Commander deck around this commander and theme. Ask about my budget and playgroup first, verify the complete 100-card list, and show what I still need.
Read this public deck URL and compare it with my saved deck. Explain the differences and validate the list before proposing an import.
Explain this card interaction using Oracle text, rulings and numbered current rules. Tell me which board-state details you still need.
Show my lab run's progress and each engine's results, including uncertainty and games that were not scored.
Clients that support MCP prompts also expose review_deck, build_commander and rules_question. Ordinary requests work too.
save_research stores private research notes directly, and review_research records a choice you state. These never install a build, approve a purchase, move inventory or promote a planner swap. Changed research evidence is flagged beside your retained answers.
Tools that edit a deck, plan, collection or lab run first create a pending proposal. Review it in Decks → Suggested changes, then choose Apply or Discard. Applying a deck edit saves a new version; stale edits are rejected if the target has changed.
Ask Claude inside Yama cannot apply its own proposals. An external MCP client also has apply and discard tools; it is instructed to apply only after you approve that exact change. Your client's permission settings control its tool calls.
A connection can read your Yama decks, collection and plans; other accounts' private data is not accessible. Information returned to an external assistant is processed by that assistant's provider. Use your own account and review the access page before connecting.
Public research uses Scryfall, EDHREC, Commander Spellbook, Wizards and supported public deck hosts. EDHREC receives the public commander or theme; ownership filtering stays in Yama. Matching a private deck against Spellbook combos requires an explicit request to share its card names and quantities. It does not send your deck name, notes or collection.
Manage and disconnect OAuth connections in Plan settings → Connected apps. Revoke script keys separately on the same page. See Yama's privacy policy.
45 tools, checked 27 October 2026. Availability depends on the caller: Ask Claude omits apply and discard. Expand a group for the tool names your client may display.
find_cardscardsearch_scryfallcard_printingsrules_lookupresearch_sourcesoverviewdeckcheck_listdeck_analysiscompare_decksdeck_historypublic_deckedit_decksave_deckcommander_recommendationsfind_combossample_handsmana_probabilitymana_testcollection_cardsadd_to_collectionmove_cardsset_conditionplan_deckreview_queuepropose_swapanswer_reviewmark_boughtmark_installedswap_in_printslab_runslab_runlab_gamespreconstart_lab_runmore_lab_gamesrun_lab_againcancel_lab_runresearchsave_researchreview_researchchangesapply_changediscard_changePrompts: review_deck, build_commander, rules_question. Resources: yama://research/sources, yama://research/format, yama://deck/{deck_id} and yama://card/{oracle_id}. Deck and card resources use the same authentication as the tools.
This is a Commander-focused toolset. Limited drafting, constructed sideboards and tournament metagame feeds are outside its current scope. Public providers may block automated access or be temporarily unavailable; failures are reported rather than treated as empty results.
/mcp is not the sign-in flow; start authentication from the client.codex mcp login yama; in Claude Code, use /mcp. Check that you chose the Yama account containing your decks.Need help? Contact Bryan. Include the client and error message, keeping tokens and private deck details out of public reports.