Skip to main content
Glama

lichess-mcp

Use with Claude PyPI Python License: MIT

An MCP server that puts the Lichess public API in front of any MCP-compatible agent, so you can ask about chess in plain language instead of reading JSON.

"How did Magnus do in blitz this week, and what did the engine think of his last loss?"

No API key, no account, no OAuth — every tool here uses Lichess' public endpoints.

What you get

Tool

What it answers

get_user_profile

Ratings in every format, title, country, account stats, current win/loss streak

get_recent_games

Recent games with PGN, result, opponent, opening and accuracy; filter by format or colour

get_game_analysis

Per-side accuracy and ACPL, plus every blunder/mistake/inaccuracy with the engine's preferred move and the eval swing

get_opening_stats

Win/draw/loss and score% for one opening, for one player, as a given colour

analyze_position

Top engine lines for a FEN, from Lichess' cloud evaluation cache, rendered in SAN

get_puzzle_of_day

Today's daily puzzle: FEN, themes, rating, and the solution

search_players

Autocomplete a half-remembered username

get_tournament_info

Arena or Swiss tournament: time control, player count, games played, standings

Plus a resource, lichess://api-reference, summarising the endpoints behind each tool, the rate limits, and the known gaps — so an agent can read the manual instead of guessing.

Output is shaped for reading, not parsing

Raw Lichess payloads bury the result of a game under ninety clock timestamps. Every tool here returns a small dict with obvious keys:

// get_recent_games("DrNykterstein", count=1, format="blitz")
{
  "game_id": "kAdOQKeh",
  "url": "https://lichess.org/kAdOQKeh",
  "played_at": "2026-04-08T19:39:03+00:00",
  "format": "blitz",
  "time_control": "3+0",
  "opening": "Alekhine Defense: Sämisch Attack",
  "color": "black",
  "result": "win",
  "my_rating": 3145,
  "rating_change": 8,
  "my_accuracy": 93,
  "opponent": { "username": "respects_55", "rating": 2644, "accuracy": 89 },
  "pgn": "[Event \"Take Take Take Arena\"]\n..."
}

Engine lines come back as SAN, because 1... e5 2. g3 Nf6 is legible and e7e5 g2g3 g8f6 is not. Evaluations are normalised so a positive score always favours the side to move, and forced mates are reported as mate_in rather than a huge centipawn number.

Related MCP server: Chess.com MCP Server

Install

Requires Python 3.10+.

uvx lichess-mcp

or

pip install lichess-mcp

Claude Desktop

Add this to your claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json, Windows: %APPDATA%\Claude\claude_desktop_config.json), then restart Claude Desktop:

{
  "mcpServers": {
    "lichess": {
      "command": "uvx",
      "args": ["lichess-mcp"]
    }
  }
}

If you installed with pip rather than using uvx, point at the installed script instead:

{
  "mcpServers": {
    "lichess": {
      "command": "lichess-mcp"
    }
  }
}

Claude Code

claude mcp add lichess -- uvx lichess-mcp

Try these

  1. "What's DrNykterstein's blitz rating, and is he on a streak right now?"get_user_profile

  2. "Show me my last 5 rapid games as Black and tell me which openings went badly."get_recent_games, then get_opening_stats

  3. "Pull up today's Lichess puzzle and give me the position — don't tell me the answer yet."get_puzzle_of_day

  4. "Here's a FEN from my game — r1bqkbnr/pppp1ppp/2n5/4p3/2B1P3/5N2/PPPP1PPP/RNBQK2R b KQkq - 3 3. What does the engine want to play?"analyze_position

  5. "Find every blunder in lichess.org/dmvL2duu and explain what each one missed."get_game_analysis

Openings, tournaments and player search work the same way: "How do I score with the Sicilian as White over my last 200 games?", "Who won tournament W1OrjDLM?", "There's a player called something like 'penguin' — find them."

Configuration

Everything is optional.

Variable

Default

Purpose

LICHESS_API_TOKEN

unset

A personal access token. Raises your rate limit and unlocks your own private data. Nothing here requires it.

LICHESS_MCP_MIN_INTERVAL

1.0

Seconds between requests. Lichess asks for 1 req/sec; lower it only with a token and a good reason.

LICHESS_MCP_MAX_RETRY_AFTER

60

Longest 429 back-off to sit out before reporting the rate limit to the caller.

LICHESS_MCP_TIMEOUT

30

Per-request timeout in seconds.

LICHESS_MCP_HTTP_LOG_LEVEL

WARNING

Set to INFO to log every outgoing request.

Being a good API citizen

Lichess is free, donation-funded, and asks clients for at most one request per second. This server enforces that globally with an async rate limiter rather than trusting each tool to behave, and backs off politely on HTTP 429. That means tools which scan many games (get_opening_stats with a large max_games) are deliberately unhurried.

If you want the whole games database, take it from database.lichess.org, not from this server.

Known limits

  • Computer analysis is opt-in on Lichess. get_game_analysis and the accuracy fields only have data for games where a player requested analysis. Games without it return analysis_available: false and say so, rather than failing.

  • analyze_position reads a cache, not a live engine. Lichess' cloud eval covers positions someone has already analysed — common openings and popular games. Novel positions return cached: false with an explanation.

  • get_opening_stats samples recent games. Lichess' personal opening explorer now requires OAuth, so this aggregates the games export instead. Results describe the last max_games games (default 200, max 500), not a lifetime total.

  • Streaks are derived, not fetched — Lichess has no streak endpoint, so get_user_profile computes the current run from the 30 most recent rated games.

Development

git clone https://github.com/Anay704/lichess-mcp
cd lichess-mcp
python -m venv .venv && .venv/bin/pip install -e ".[dev]"
.venv/bin/pytest                             # offline, sub-second
.venv/bin/ruff check .

The suite stubs the HTTP layer, so the default run is fast and works offline. A handful of tests that really call lichess.org are opt-in:

LICHESS_MCP_LIVE_TESTS=1 .venv/bin/pytest

License

MIT — see LICENSE.

Not affiliated with or endorsed by Lichess. Lichess is a free/libre, open-source chess server; if you get value out of this, consider donating to them.

Install Server
A
license - permissive license
A
quality
C
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

  • A
    license
    C
    quality
    D
    maintenance
    An MCP server that enables natural language interaction with the Lichess chess platform, allowing users to play games, analyze positions, manage their account, and participate in tournaments through Claude.
    Last updated
    90
    8
    17
    MIT
  • A
    license
    B
    quality
    D
    maintenance
    Provides access to Chess.com player data, game records, and public information through standardized MCP interfaces, allowing AI assistants to search and analyze chess information.
    Last updated
    10
    79
    MIT
  • F
    license
    A
    quality
    C
    maintenance
    Enables chess analysis and move generation using the Stockfish engine via MCP tools, allowing clients to evaluate positions, get best moves, apply moves, and visualize boards.
    Last updated
    7

View all related MCP servers

Related MCP Connectors

  • MCP server exposing the Backtest360 engine API as tools for AI agents.

  • MCP server for AI dialogue using various LLM models via AceDataCloud

  • MCP server for Argo RPG Platform — connects AI assistants to campaign data via OAuth2

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Anay704/lichess-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server