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_profileC | |
| get_chess_player_statsC | |
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 have clearly distinct purposes: one retrieves a player's profile information, the other retrieves their game statistics. There is no ambiguity about which tool to use based on the resource sought.
Both tools follow the exact same get_chess_player_<resource> pattern, making the naming convention perfectly consistent and predictable. An agent can infer future tools would likely follow this pattern.
At 2 tools, the server is at the borderline low end. While the tools are relevant, the server name 'Chess.com MCP Server' implies a broader domain, and this small count feels thin compared to the potential feature surface.
The server covers only profile and stats for a player, but omits many core Chess.com resources such as games, tournaments, leaderboards, or club information. Significant gaps remain that would require additional tools to handle common workflows.