Chess MCP Server
Enables AI assistants to retrieve Chess.com player profiles, statistics, and daily puzzles through the Model Context Protocol.
README
Chess MCP Server
A Model Context Protocol (MCP) server that provides seamless access to Chess.com API data through AI assistants like Claude, ChatGPT, and others.
MCP Resources
- Official Documentation: Model Context Protocol
- GitHub Repository: modelcontextprotocol
- Specification: MCP Specification
Project Architecture
This Chess MCP Server provides three main tools:
getPlayerProfile- Retrieve player information and statisticsgetPlayerStats- Get detailed player ratings and performance datagetDailyPuzzle- Access the daily chess puzzle
Quick Start
Prerequisites
- Node.js 18.0.0 or higher
- npm or yarn package manager
Installation
-
Clone the repository
git clone https://github.com/dipalosalvatore/chess-mcp-server.git cd chess-mcp-server -
Install dependencies
npm install -
Build the project
npm run build -
Start the server
npm start
Docker Support
Using Docker
-
Build the Docker image
docker build -t chess-mcp-server . -
Run the container
docker run -it chess-mcp-server
Docker Configuration for MCP Clients
When using Docker, update your MCP client configuration to use the Docker container:
Claude Desktop with Docker
{
"mcpServers": {
"chess": {
"command": "docker",
"args": ["run", "-i", "--rm", "chess-mcp-server"],
"env": {}
}
}
}
MCP Configuration
For Claude Desktop
- Open Claude Desktop settings
- Navigate to "Servers" section
- Add a new server with these settings:
{
"name": "Chess MCP Server",
"command": "node",
"args": ["/path/to/chess-mcp-server/dist/index.js"],
"env": {}
}
For Other MCP Clients
Most MCP clients support similar configuration. The server communicates via stdin/stdout, so you'll need to specify:
- Command:
node - Arguments:
[path-to-dist/index.js] - Working Directory: Your project directory
Example Configuration Files
Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"chess": {
"command": "node",
"args": ["/Users/username/projects/chess-mcp-server/dist/index.js"],
"env": {}
}
}
}
ChatGPT (if supported)
{
"servers": [
{
"name": "Chess Server",
"command": "node",
"args": ["dist/index.js"],
"cwd": "/path/to/chess-mcp-server"
}
]
}
Available Tools
1. Get Player Profile
Retrieves comprehensive player information from Chess.com.
Tool Name: getPlayerProfile
Parameters:
username(string, required): Chess.com username
Example Usage:
Get the profile for player "magnuscarlsen"
2. Get Player Stats
Retrieves detailed player statistics and ratings.
Tool Name: getPlayerStats
Parameters:
username(string, required): Chess.com username
Example Usage:
Get statistics for player "hikaru"
3. Get Daily Puzzle
Retrieves the current daily puzzle from Chess.com.
Tool Name: getDailyPuzzle
Parameters: None
Example Usage:
Get today's chess puzzle
Development
Building from Source
# Install dependencies
npm install
# Type checking
npm run type-check
# Build the project
npm run build
Project Structure Details
Chess API Wrapper (src/chess/)
The chess API is organized into specialized classes:
PlayerApi- Player profiles, stats, and game historyPuzzleApi- Daily puzzles and random puzzlesCommunityApi- Clubs, tournaments, and teamsBaseChessApi- Common functionality and HTTP client setup
MCP Tools (src/tools/)
Each tool is implemented as a function that:
- Validates input using Zod schemas
- Calls the appropriate Chess.com API
- Returns standardized MCP responses
- Handles errors gracefully
Error Handling
The server provides comprehensive error handling:
- Validation Errors (400) - Invalid input parameters
- Not Found Errors (404) - Player or resource not found
- Rate Limit Errors (429) - API rate limit exceeded
- Server Errors (5xx) - Chess.com API issues
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Development Setup
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
License
This project is licensed under the MIT License - see the LICENSE file for details.
Acknowledgments
- Chess.com for providing the API
- Model Context Protocol for the MCP standard
- Anthropic for Claude and MCP support
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.