chess.com MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_chess_player_profileB | Get the public profile for a Chess.com player by username. |
| get_chess_player_statsB | Get the stats for a Chess.com player by username. |
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 2 tools
The two tools are clearly distinct: one retrieves a player's profile, the other retrieves their stats. There is no overlap or ambiguity in their purposes.
Both tool names follow the identical pattern 'get_chess_player_<resource>', using consistent snake_case and the same verb-noun structure. This makes the naming highly predictable.
With only 2 tools, the server feels thin for a domain as broad as chess.com. This is at the borderline where a 1-2 tool set is acceptable if scoped tightly, but it limits overall usefulness.
The server covers only player profile and stats, missing common chess.com resources like games, tournaments, and leaderboards. This is a significant gap for a server claiming to represent the chess.com API, likely causing agent failures for broader queries.