FFE MCP
Related Servers
Alternatives to FFE MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables querying Chess.com public data including player profiles, stats, games, and club information through natural language.94 npmMIT
- 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
- AlicenseBqualityAmaintenanceEnables natural-language access to Chess.com's public API, exposing player, club, tournament, puzzle, and leaderboard data through tools and resources without authentication.3045 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables natural language interaction with Lichess chess platform to play games, analyze positions, manage challenges and tournaments, and interact with other players through Claude Desktop.16 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to explore player profiles, ratings, game archives, leaderboards, clubs, and puzzles via the Chess.com API.2MIT
- AlicenseAqualityDmaintenanceConnects Claude to Lichess for playing chess games, analyzing positions with Stockfish cloud evaluation, and solving puzzles. Supports real-time gameplay including moves, challenges, draw offers, and accessing user profiles and game history.2816 npmMIT
TDQS
Scored across 5 tools
Every tool targets a distinct query: player search, tournament listing, tournament details, tournament standings, and individual player results. There is no meaningful overlap between any two tools.
All names are lowercase snake_case in French and clearly readable. The slight split between verb-led names (rechercher_joueur, lister_tournois) and noun-led names (details_tournoi, classement_tournoi, resultats_joueur_tournoi) is a minor inconsistency rather than a real problem.
Five tools is well-scoped for a read-only French chess federation data server. Each tool earns its place and there is no redundant tooling.
The set covers the central public workflows: searching players, discovering tournaments, getting tournament metadata, viewing final standings, and looking up individual round-by-round results. Minor gaps such as a full player profile or tournament pairings per round exist, but the core surface is coherent and usable.