Skip to main content
Glama

Related Servers

Alternatives to ygopro-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to adjudicate Yu-Gi-Oh! rulings against real ocgcore Lua scripts and engine simulations, build and validate banlist-legal decks, analyze matchups and meta trends, and compare card prices across US/JP/AE markets. It also supports card and rulebook lookup, tournament paperwork, and custom-card tooling.
      4
      56
      439 npm
      AGPL 3.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to control a Minecraft bot and interact with the game through MCP tools, including observing state, moving, mining, crafting, building, farming, managing inventory, enchanting, and chatting in-game.
      1
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables tool-using language models to play Lemonade Tycoon Deluxe as a text-only business benchmark, exposing game UI state and actions as semantic MCP tools without vision or shell access.
      23
      MIT
    • 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.
      5
      BSD Zero Clause
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to autonomously create characters, join matchmaking, and battle other LLMs in a turn-based game using 7 tools for status, abilities, and actions.
      ISC
    • A
      license
      A
      quality
      B
      maintenance
      Enables LLM agents to play full games of Civilization VI by connecting to running game instances via the FireTuner debug interface, with 76 tools for units, cities, diplomacy, research, and turn management, plus narration of game state through rule-enforcing APIs without requiring vision models.
      80
      MIT

    TDQS

    A3.6/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools map to distinct duel-control lifecycle stages (lobby, deck, ready, start, prompt, act, surrender), so selection is usually clear. The main overlap is the prompt-response group: control_act and control_act_id both submit a decision and differ mainly by encoding, though the raw-vs-semantic descriptions help.

    Naming Consistency4/5

    All names share a consistent control_ namespace and snake_case formatting, making the set easy to scan. However, suffixes mix nouns (state, lobby, chat) and verbs (act, start, join) rather than following a pure verb_noun pattern.

    Tool Count5/5

    Fourteen tools are well within a reasonable range for controlling a duel client, and each covers a distinct concern: session setup, prompt loop, action submission, state inspection, surrender, chat, and health. The debug/health/msg tools are minor extras but do not feel like bloat.

    Completeness4/5

    The surface covers join, deck preload, ready, start, prompt handling, action execution, state inspection, surrender, and chat, which is most of the duel session lifecycle. Minor gaps remain around explicit disconnect/leave and room creation or listing, with some room state visible only through chat or raw messages.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues