Skip to main content
Glama

YGO Judge

Settle Yu-Gi-Oh! ruling questions with ChatGPT or Claude. YGO Judge is an MCP server that lets either assistant use EDOPro's rules engine. It builds the board, plays both players, answers from what the engine actually does, and checks Konami's official Q&As.

You: My opponent activates Reinforcement of the Army. I chain Ash Blossom, and they chain Called by the Grave on my Ash. Does the search still happen?

The assistant sets up that board and plays it out. This is the log the engine produces:

Chain Link 1: P1 activates Reinforcement of the Army (P1 Spell & Trap Zone 1)
Chain Link 2: P2 activates Ash Blossom & Joyous Spring (P2 hand): "Negate that effect"
Ash Blossom & Joyous Spring: P2 hand → P2 GY — discarded, as a cost
Chain Link 3: P1 activates Called by the Grave (P1 Spell & Trap Zone 2)
Targets: Ash Blossom & Joyous Spring (P2 GY)
Resolving Chain Link 3 (Called by the Grave)
Ash Blossom & Joyous Spring: P2 GY → P2 banished — by an effect
Resolving Chain Link 2 (Ash Blossom & Joyous Spring)
Chain Link 2 (Ash Blossom & Joyous Spring): its effect is negated
Resolving Chain Link 1 (Reinforcement of the Army)
Marauding Captain: P1 Deck → P1 hand — by an effect

The assistant then answers with the verdict and the reasoning, and can hand you the board as an EDOPro puzzle file so you can replay it yourself.

How it works

  • The engine is EDOPro's core (edo9300/ygopro-core), the C++ library that runs every EDOPro duel. It uses the Project Ignis card scripts and card databases. It runs headless: no EDOPro window, lobby or decks.

  • The harness talks to the engine through ctypes. Every engine prompt becomes a numbered list of options for the player who has to decide, and the assistant answers by number or by option text. Only response windows with no legal effects and forced choices are skipped. Zones, battle positions, card ordering and legal responses are chosen explicitly. The log is written the way a judge would describe the chain.

  • Boards are EDOPro puzzle scripts. Every scenario the assistant builds opens in EDOPro's Puzzle mode, where one person controls both players.

  • Duels are saved as their list of answers. The engine is deterministic, so undo and server restarts replay them only when the engine, scripts, card data and harness rules still match.

  • Rulings come from the YGOrg card database: Konami's FAQ entries and Q&As, translated, and cached locally.

Related MCP server: mcp-ygoprodeck

Tools

Tool

What it does

find_card

Looks up cards by (fuzzy) name or passcode, with full text and stats

start_duel

Builds a board on P1's turn 1 and stops at the first legal decision. Covers hand, field, GY, banished, Deck, Extra Deck, summon type, Xyz Materials, equips, continuous targets, counters and LP

choose

Answers decisions by option number or text; several can be queued

get_state

Board, full log and the pending decision

undo

Takes back decisions to try the other branch

export_puzzle

The board as an EDOPro puzzle (.lua), with a download link

get_rulings

Konami's FAQ for each card and the Q&As that involve all of them

card_script

A card's Lua script, i.e. exactly how the engine implements it

There's also a judge prompt that takes a ruling question.

Turn and phase rules

Every test starts on P1's turn 1 and stops at the first legal decision, usually Main Phase 1. Legal Draw/Standby Phase activation windows are shown too. Normal first-turn rules apply: P1 cannot enter the Battle Phase or Main Phase 2 on that turn. An effect that requires Main Phase 2, such as The Flute of Guiding Dragon's Graveyard draw effect, cannot be used on turn 1.

To test going second, put that player's cards in p2 and use choose to end P1's turn. End P2's turn as well to reach P1's next turn (turn 3). Check the turn and phase shown in the result before drawing a conclusion. Cards that must have been sent to the GY this turn must actually be sent there during that turn; placing them in the starting GY does not reproduce that history.

Normal Draw Phase draws apply from turn 2 onward. Decks are empty unless supplied: include cards or deck_filler when advancing turns, or the player can lose by being unable to draw. The starting Deck order is top card first; subsequent shuffles happen normally and are deterministic for a given seed. No opening hand is drawn because the scenario explicitly supplies the players' hands.

Scenario history and decisions

For revival-restricted monsters in the GY or banished zone, specify whether the required summon procedure was completed. A bare name is rejected when that history is needed. For example:

{
  "p1": {
    "hand": ["Monster Reborn"],
    "graveyard": [{"card": "Stardust Dragon", "properly_summoned": true}]
  }
}

Use false if it was sent directly from the Extra Deck. These entries also accept summoned and summoned_from when the previous summon matters. Field monsters accept properly_summoned too; a natural Fusion/Ritual/Synchro/Xyz/Link summon implies completion by default, while other summon histories for restricted monsters require an explicit value. Other events, used effects and this-turn restrictions must still be played out. Unsupported setup fields are rejected.

Every meaningful decision is shown, including all legal response windows, zones, battle positions, card ordering and rock-paper-scissors. The old stop_at_every_window option has been removed; this behavior is always enabled. Pass explicitly when declining a legal response. Integer choices are zero-based option indices; string choices match labels first. For Reasoning, "7" declares Level 7, while integer 7 chooses option index 7 (Level 8).

Engine/card-script errors invalidate a simulation. Fix the cause and start a new duel; an unavailable effect in a failed simulation is not evidence that the activation is illegal.

Saved-duel compatibility

Older versions changed first-turn phases, normal draws, shuffling and decision handling. Their saved duels must be restarted with start_duel and retested. Saved duels now include a fingerprint of the engine binary, card scripts, databases and strings as well as a harness rules version. Asset changes require a fresh duel instead of replaying answers against different code. Restart the server after changing local engine/card assets; container updates already restart it.

Every image build runs the regression suite against its bundled engine and card data before it can publish. Pull requests build and test the image without publishing it.

Connect ChatGPT or Claude

Both clients use the same server URL:

https://<your host>/<access key>/mcp

ChatGPT

In ChatGPT Plugins on the web, select + → Add custom MCP server. Name it YGO Judge, enter the server URL above, and select No authentication. Create the plugin, install it, then start a Work chat and mention @YGO Judge when asking a ruling question.

Claude

On claude.ai or Claude Desktop, go to Settings → Connectors → Add custom connector and enter the same server URL.

The connector then also works in the Claude iOS and Android apps. Free Claude accounts can add one custom connector. Then just ask your question.

The access key is a secret part of the URL. Requests without it get a 404, so treat the URL like a password even though ChatGPT's connection uses No authentication.

Self-hosting

The image ghcr.io/lukaznj/ygo-judge is built for linux/arm64 (Raspberry Pi 4/5, Apple silicon); for x86 servers, build it yourself from the Containerfile. It is rebuilt every week with the latest engine, card scripts and databases. The server needs about 100 MB of RAM.

Docker Compose or Portainer

compose.yml works with docker compose up -d and as a Portainer stack (Stacks → Add stack → Web editor, paste the file). Set two variables:

Variable

What it is

STATE_DIR

Host folder for the access key, saved duels and the rulings cache. Use an absolute path in Portainer.

PUBLIC_URL

The address people reach the server at, e.g. https://ygo-judge.example.com. Used for puzzle download links.

Put a reverse proxy with HTTPS in front of 127.0.0.1:8010, e.g. Nginx Proxy Manager, Caddy or a Cloudflare Tunnel. On first start the server creates its access key in STATE_DIR/access_key and prints the connector URL in its log.

Updates are automatic. The stack includes Watchtower, which checks for a new image every hour and redeploys the judge when there is one. It only touches containers labelled com.centurylinklabs.watchtower.enable=true.

Development

scripts/fetch-data.sh    # vendor/: engine source, card scripts, databases, strings.conf
scripts/build-engine.sh  # build/libocgcore.dylib (or .so)
uv run pytest
uv run ygo-judge         # http://127.0.0.1:8000/<access key>/mcp, key in state/access_key

File

What it holds

src/ygo_judge/engine.py

ctypes binding to the engine's C API

src/ygo_judge/messages.py

Decoder for the engine's binary messages

src/ygo_judge/scenario.py

Board setups, written as EDOPro puzzle scripts

src/ygo_judge/duel.py

Decisions, automatic answers, the log, the board and undo

src/ygo_judge/cards.py

Card data, scripts and strings

src/ygo_judge/rulings.py

YGOrg client with a disk cache

src/ygo_judge/server.py

MCP tools and HTTP routes

Accuracy

The engine is not a judge. Project Ignis scripts follow OCG rulings, TCG rulings sometimes differ, and scripts can have bugs, especially for new cards. That's why the assistant is told to:

  • check the official Q&As;

  • say when the engine and the rulings disagree;

  • pass on any script errors the engine reports.

Things that happened earlier in a turn can't be written into a board setup; they have to be played out. Examples are a Normal Summon already used, or a once-per-turn effect already activated.

License

AGPL-3.0-or-later. The engine and the card scripts this server runs are AGPL-3.0, so the server is too. If you host a modified version, share its source with its users.

YGO Judge is not affiliated with Konami. Yu-Gi-Oh! is a trademark of Konami and Kazuki Takahashi. Credit for the engine goes to edo9300 and the YGOPro contributors, for the card scripts and databases to Project Ignis, and for the rulings translations to the YGOrganization database team.

Related MCP Connectors

Related MCP Servers

  • 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
    -
  • A
    license
    Not graded
    quality
    C
    maintenance
    Provides Yu-Gi-Oh! card data, banlist, deck management, OCG rules engine, duel simulation, replay analysis, and YGOPro2 bridge for AI agents via MCP.
    4
    BSD Zero Clause