Chess.com MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NO_UV | No | Set to 1 to bypass uv path issues when running with UV. | |
| MCP_HOST | No | Listen address for the HTTP server. | 0.0.0.0 |
| MCP_PORT | No | Listen port for the HTTP server. | 8000 |
| OAUTH_ISSUER | No | Expected token issuer. | https://auth.smartpage.cl/realms/casa |
| OAUTH_JWKS_URL | No | Where signing keys are fetched. | http://192.168.1.46:8080/realms/casa/protocol/openid-connect/certs |
| MCP_RESOURCE_URL | No | Public MCP URL, expected token audience. | https://chess.smartpage.cl/mcp |
| MCP_ALLOWED_HOSTS | No | Accepted Host headers (DNS rebinding protection). | localhost:*,127.0.0.1:* |
| OAUTH_ALLOWED_CLIENTS | No | Accepted azp values. | claude-chess-mcp |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_player_profileC | Get a player's profile from Chess.com |
| get_player_statsC | Get a player's stats from Chess.com |
| get_player_current_gamesC | Get a player's ongoing games on Chess.com |
| get_player_games_by_monthB | Get a player's games for a specific month from Chess.com |
| get_player_game_archivesC | Get a list of available monthly game archives for a player on Chess.com |
| get_titled_playersC | Get a list of titled players from Chess.com |
| get_club_profileC | Get information about a club on Chess.com |
| get_club_membersC | Get members of a club on Chess.com |
| download_player_games_pgnC | Download PGN files for all games in a specific month from Chess.com |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools target clearly distinct resources: player profile, stats, current games, archives, clubs. The only mild overlap is get_player_games_by_month versus download_player_games_pgn, both scoped to a month's games, but the descriptions distinguish JSON data vs PGN file download.
All names are snake_case verb_noun with a uniform get_ prefix except the single download_player_games_pgn. The deviation is meaningful and readable, but it is still a break from the otherwise uniform pattern.
9 tools is squarely in the well-scoped range, with each tool mapping to a distinct Chess.com read endpoint. No filler or trivially redundant entries.
Player, game history, archives, PGN export, and club data are well covered, giving a coherent read-only surface. Gaps remain: no player search by name (only titled players), no single-game lookup, and no tournament or puzzle endpoints.