Everything a session needs is here in sequence: authenticate, challenge a player or Stockfish, stream the board, move, and finish with a draw, a resignation or an abort. Moves go in as UCI text (e2e4, e7e8q for promotion), so the model has to hold the position itself — nothing here renders a board, and lichess_cloud_eval is Lichess' cloud analysis rather than an engine on your machine. The read side is wider than the play side, covering puzzle history, rating history, crosstables and leaderboards for players you never face.
A 28-tool server over a Lichess account: the games it is playing, the challenges waiting on it, its puzzle history, and the public profiles and leaderboards around it.
- OAuth sign-in through a browser, and a status check on which account is connected
- Challenges in both directions — sent with a chosen time control, colour and rated flag, then listed, accepted, declined or cancelled — plus games against Stockfish at level 1–8
- Live play: UCI moves, draw offers and replies, takebacks, resignation, aborts within the first few moves, and in-game chat
- The board streamed as it changes, and an account-level event stream carrying game starts and incoming challenges
- Your game history and ongoing games with moves, result, opponent, time control and opening
- Cloud Stockfish evaluation of any FEN position, returning the best move, score and top lines
- Puzzles and standings — the daily puzzle, one by ID, your next recommended one, your attempt history, plus profiles, rating history, head-to-head crosstables and leaderboards
A Lichess account, connected through the OAuth flow that lichess_auth_start opens in a browser — the tools that read your games, play a move or answer a challenge all act as that account.
One command plus a key — npx -y @smithery/cli install @karayaman/lichess-mcp --client claude, then supply credentials