Skip to content
Open app Talk to sales
Chess.com logo

Chess.com MCP server

Access Chess.com player data

Chess.com is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Start building See the Chess.com integration
Tools
3
Works with
Any MCP client
License
MIT, open source
Updated
August 2026

About the Chess.com MCP server

Connect Chess.com once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Chess.com and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Chess.com tools your AI can run

Once connected, your assistant can call any of these Chess.com actions by asking in plain language.

  • Get Player Profile

    Retrieve a Chess.com player's public profile by username (avatar, country, join date, followers).

    1 field

  • Get Player Stats

    Retrieve a Chess.com player's ratings and W/D/L for rapid, blitz, bullet, and chess960.

    1 field

  • Get Daily Puzzle

    Retrieve today's Chess.com daily puzzle.

Give your assistant Chess.com

Connect Chess.com once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Get your server URLTalk to sales

Chess.com MCP, answered.

No. That is the point of it. One Activepieces server exposes Chess.com alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Chess.com in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 3 tools, including Get Player Profile, Get Player Stats, Get Daily Puzzle, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.