Skip to main content
Glama

Related Servers

Alternatives to Chess MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to play and analyze chess, validate moves, and view a live synchronized visual board in the browser through MCP tools.
      17 npm
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to play chess against users, manage games, make moves, and visualize boards with Stockfish AI opponent.
      8
      1
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A server that enables users to play chess against any LLM, with features for visualizing the board, making moves in standard notation, and analyzing positions from PGN files.
      23
      Apache 2.0
    • F
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to play, analyze, and track chess games with full rule validation and support for standard algebraic notation. It provides tools for position evaluation and game state persistence during user sessions.
      2
      -
    • A
      license
      B
      quality
      B
      maintenance
      Enables two autonomous LLM agents to play a full game of chess against each other over MCP, with turn order, legality, clocks, and move history enforced server-side outside both models so neither player can cheat or desync the position, while a live WebSocket GUI lets spectators watch.
      11
      MIT
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      A Model Context Protocol server that enables LLM agents and humans to play chess games together with comprehensive game management capabilities including move validation, draw detection, and game state tracking.
      -

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct role: createGame starts a game, joinGame enters an existing game, waitForNextTurn blocks until the agent's turn, and finishTurn submits a move. There is no meaningful boundary overlap between these operations.

    Naming Consistency5/5

    All tool names use the same imperative camelCase style and mostly follow a verb + object pattern: createGame, joinGame, waitForNextTurn, finishTurn. The naming is predictable and consistent across the set.

    Tool Count5/5

    Four tools is well-scoped for a turn-based chess workflow: create, join, wait, and move. Each tool earns its place and there are no redundant tools.

    Completeness4/5

    The core chess lifecycle is covered: start or join a game, wait for a turn, submit a move, and get updated state. Minor optional gaps remain, such as resigning, listing active games, or an explicit get-board/status tool, but agents can work around these using the returned board state.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues