Chess.com MCP

Chess.com MCP wraps the Chess.com public API into a handful of MCP tools that let Claude or Cursor pull player stats, fetch game PGNs, and query profiles without any authentication dance. You point it at a username and get back Elo ratings, win-loss records, recent games, or even full archives going back years. The Docker image is tiny and starts instantly, which makes it one of the smoother one-off installs in the MCP ecosystem. I'd reach for this when I want to analyse a specific opening line across dozens of real games, or when I'm coaching someone and need to pull their blunder rate from the last month without opening a browser. The game history tool returns PGN strings, so you can pipe them straight into analysis prompts or feed them to a local engine. The profile lookup is less exciting but occasionally useful if you're building a chess-adjacent project and need to validate usernames or check if someone's titled. Quirks: it's read-only, so you can't post games or update profiles. The API rate limits are Chess.com's problem, not the server's, but if you hammer it with bulk requests you'll hit walls. The Docker-only distribution means you're running a container for what's essentially a thin HTTP wrapper, which feels heavy if you're not already containerised. No local caching either, so repeated queries for the same data hit the API every time. Skip this if you're not already working with chess data or if you just want to look up your own stats occasionally. The web interface is faster for casual use. But if you're prototyping a chess tutor agent, building a repertoire assistant, or doing any kind of systematic game analysis inside Claude, this is the cleanest way to get structured data without scraping HTML or managing API keys. It does one thing, does it well, and doesn't pretend to be more.