Skip to main content
Glama
KannanSudhakaran

chess.com MCP Server

by KannanSudhakaran
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Setting Up MCP server

This is for windows setup . You need python and uv installed on machine.If uv not installed then install using

pip install uv

Make a demo folder in windows

mkdir demo
cd demo

Initialized virtual environment

demo>uv init
demo>uv venv
demo>.venv\Scripts\activate
(demo) c:\demo>uv add mcp[cli] requests

open the folder in code

```bash
(demo) demo>code .

Add Folder src and chess

With in VS code , click on folder icon and add folder named src Inside the src folder add another folder named chess

Related MCP server: MCP Chess Server

Add File init.py

Add empty file inside chess folder __init__.py

Add chess_api.py

Add file named ```chess_api.py``` inside chess folder and add below code
import requests

CHESS_API_BASE = "https://api.chess.com/pub"
headers = {
    "accept": "application/json",
    "User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) Python/3.10"
}

def get_player_profile(username):
    url = f"{CHESS_API_BASE}/player/{username}"
    response = requests.get(url, headers=headers)
    response.raise_for_status()
    return response.json()

def get_player_stats(username):
    url = f"{CHESS_API_BASE}/player/{username}/stats"
    response = requests.get(url, headers=headers)
    response.raise_for_status()
    return response.json()

Add file server.py

Add another file named server.py inside chess folder and add below code

from mcp.server.fastmcp import FastMCP
mcp =  FastMCP("chess.com")

from .chess_api import get_player_profile, get_player_stats

@mcp.tool()
def get_chess_player_profile(username: str):
    """Get the public profile for a Chess.com player by username."""
    return get_player_profile(username)

@mcp.tool()
def get_chess_player_stats(username: str):
    """Get the stats for a Chess.com player by username."""
    return get_player_stats(username)

def main():
    mcp.run(transport="stdio")

if __name__ == "__main__":
    main()

Update the pyproject.toml file

The chess.server:main indicates there is chess folder inside src and call main method in file server.py


[project.scripts]
chess = "chess.server:main"

[build-system]
requires = ["setuptools"]
build-backend = "setuptools.build_meta"

[tool.setuptools]
package-dir = {"" = "src"}

[tool.setuptools.packages.find]
where = ["src"]

Run with MCP

demo>uv run chess

Note the command chess match [project.scripts]

There will be no output , if you get any syntax errors it will show. Just exit out of server console using Ctrl+C

Install Claude Desktop from official website

Add configuration file for Claude

Go to the folder C:\Users\{yourname}\AppData\Roaming. Or In run command type %APPDATA% .Verify that the folder contains a subfolder named Claude.

create a new file name claude_desktop_config.json

add following contents into it . Update the driectory path based on your computer eg C:\\temp\\AI\\MCP_ORL3\\demo


{
  "mcpServers": {
    "kannan-server": {
      "command": "uv",
      "args": [
        "--directory",
        "C:\\temp\\AI\\MCP_ORL3\\demo",
        "run",
        "chess"
      ]
    }
  }
}

Restart Claude Desktop ,start a new chat

Look for icon SearchAndTools below prompt textbox

You will be able to see the mcp server agent named kannan-server ,based on the name you provided in the configuration file.

Note to disable websearch. Now you can start searching for profile info and stats for Chess.com players using the commands you defined.

Available Tools

2 tools
get_chess_player_profileB

Get the public profile for a Chess.com player by username.

ParametersJSON Schema
NameRequiredDescriptionDefault
usernameYes

TDQS

B3.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. The word 'public' implies read-only access and no authentication, which is useful behavioral context. However, it does not disclose rate limits, error behavior, or response shape, so transparency is only minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no wasted words. The action and resource are front-loaded, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read-only lookup, the description is adequate for invocation. However, with no output schema or sibling guidance, an agent would not know what the profile contains or why to choose this over get_chess_player_stats, leaving notable gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, and the only parameter, 'username', is documented only by its name and type. The description's phrase 'by username' confirms the parameter's role but adds no format, validation, or additional meaning beyond what the schema already shows.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get') and the exact resource ('public profile for a Chess.com player') with the lookup mechanism ('by username'). It is specific and unambiguous, though it does not explicitly differentiate from the sibling tool get_chess_player_stats beyond the resource type itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided about when to use this tool versus get_chess_player_stats. There are no conditions, exclusions, or alternative scenarios mentioned, leaving the agent to infer selection purely from the tool name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_chess_player_statsB

Get the stats for a Chess.com player by username.

ParametersJSON Schema
NameRequiredDescriptionDefault
usernameYes

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'get' which implies a read operation, but it gives no detail about required authentication, rate limits, response behavior, or any side effects. This is thin for a remote API tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single economical sentence, with the key action and resource front-loaded. There is no unnecessary repetition or padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema, the description provides the minimum needed to understand the core call. However, it lacks any context about what 'stats' include, whether there are any prerequisites, or how this differs from the sibling tool, leaving some gaps for a fully informed decision.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description confirms that the single parameter 'username' is the player's Chess.com username, adding a small amount of meaning beyond the schema's bare property title. However, with 0% schema description coverage, it does not elaborate on expected format, case sensitivity, or potential validation, so the added value is limited.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('get'), resource ('stats'), and scope ('by username'), making the function clear. It is distinguishable from the sibling tool get_chess_player_profile because 'stats' and 'profile' are different resources, though the sibling is not explicitly referenced.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus get_chess_player_profile, and there are no exclusions or alternative routing. The only usage cue is the implicit difference between 'stats' and 'profile', which is left for the agent to infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv0.1.0
    • First observedget_chess_player_profile
    • First observedget_chess_player_stats
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 2 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count3/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • MCP Chess Server

    Ramakrishna-Gedala
    F
    license
    B
    quality
    D
    maintenance
    Enables interaction with Chess.com's public API to retrieve player profiles and statistics including rating history and performance metrics for any Chess.com username.
    2
    -

  • MCP Chess Server

    CyprianFusi
    A
    license
    B
    quality
    D
    maintenance
    Provides Chess.com player data integration, enabling AI assistants to fetch real-time chess player profiles and comprehensive statistics including ratings, game counts, and performance metrics from Chess.com's public API.
    2
    MIT

  • Chess.com MCP Server

    Gelberm
    F
    license
    B
    quality
    D
    maintenance
    Provides tools to interact with the Chess.com Public API for fetching real-time player profiles and detailed game statistics. It enables LLMs to access information like player ratings, win/loss records, and current online status.
    2
    -

  • Chess MCP Server

    bhayanak
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI assistants to explore player profiles, ratings, game archives, leaderboards, clubs, and puzzles via the Chess.com API.
    1
    MIT