Skip to main content
Glama
ChiyukiRuon

250game MCP

by ChiyukiRuon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to 250game MCP

No user-submitted related servers found.

    Related Servers

    • AutoChess MCP

      Cecilia-coding
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and web players to join shared auto-battler rooms, read turn snapshots, submit actions, and spectate deterministic matches with replays and pluggable packs/modes.
      MIT

    • balatro-agent

      KaishenChiang
      A
      license
      A
      quality
      A
      maintenance
      Windows-local MCP for Steam Balatro: tool-calling AI reads player-visible state, chooses and executes native actions, confirms results, and saves local experience. Glama's Linux sandbox can introspect MCP and run game-independent tools such as calculate, but cannot connect to Balatro on the user's Windows machine. Without the local game, health reports disconnected.
      4
      12
      3
      MIT

    • rain-go

      SerenQi
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI and humans to play 10 board, card, and dice games together via MCP tools, with seat-based multiplayer and server-side hidden-hand isolation.
      22
      MIT

    • Tesseron

      tesseron-dev
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible AI agents to execute typed live-app actions over WebSocket, allowing agents to directly interact with real application state without browser automation or scraping.
      21
      Business Source 1.1
    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.5/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools map to clearly separate actions (join/leave, draw/discard, chat send/read, state/wait). The main overlap is among play_cards, select_cards, and select_put_method, plus respond_cha vs respond_anti_calc, but descriptions disambiguate each by the pending.kind or phase they target, so an agent can still choose correctly with the state returned by get_state.

    Naming Consistency5/5

    All 16 names use snake_case with a consistent verb_noun pattern (get_state, set_ready, play_cards, draw_card, respond_cha, join_game, send_chat, etc.). Domain jargon like 'cha' and 'calc' appears, but it stays within the same predictable naming convention.

    Tool Count4/5

    16 tools is at the high end but justified by a multi-phase card game with distinct pending-response steps (putMethod, cards, cha, anti-calc). Each tool maps to a real gameplay or session operation rather than duplicate surfaces, so the count is slightly heavy but reasonable.

    Completeness4/5

    The surface covers the full session lifecycle: join/leave/reconnect, ready, play/draw/discard, all pending response phases, round-ending calc, chat, profile, state polling, and waiting. Minor gaps exist (no explicit reconnect or room-list tool), but join_game with playerId lets agents work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources