MCP Chess Server
Related Servers
Alternatives to MCP Chess Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables querying Chess.com player profiles and stats using the Chess.com API.2-
- FlicenseBqualityDmaintenanceProvides 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-
- -licenseNot gradedqualityNot gradedmaintenanceProvides access to Chess.com's public API, allowing AI assistants to fetch player information and statistics.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query Chess.com's public API for player profiles, stats, game archives, online status, clubs, and titled players, and to download game PGNs.MIT
- AlicenseBqualityDmaintenanceProvides 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.2MIT
- AlicenseBqualityAmaintenanceEnables natural-language access to Chess.com's public API, exposing player, club, tournament, puzzle, and leaderboard data through tools and resources without authentication.3077 npmMIT
TDQS
Scored across 2 tools
The two tools have distinct purposes: one retrieves a player's profile (likely general info), and the other retrieves stats (likely performance data). While both target the same resource (a Chess.com player), the actions are clearly differentiated, making misselection unlikely. However, the overlap in domain could cause minor confusion if an agent needs both types of data, but descriptions help clarify.
Both tools follow a consistent verb_noun pattern with 'get_chess_player_' as a prefix, followed by 'profile' or 'stats'. This predictable naming scheme makes it easy for agents to understand and navigate the tool set without ambiguity or mixed conventions.
With only 2 tools, the server feels thin for a chess domain, as it lacks operations like creating games, making moves, or accessing game history. While it might be narrowly scoped to player data retrieval, the limited count suggests incomplete coverage for typical chess-related tasks, bordering on under-scoped.
The tool set is severely incomplete for a chess server, as it only provides read-only access to player data with no ability to interact with games, boards, or other chess elements. There are significant gaps in CRUD/lifecycle coverage, such as missing create, update, or delete operations, which will likely cause agent failures in broader chess-related workflows.