mcp-server-codeforces
Related Servers
Alternatives to mcp-server-codeforces
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceConnects AI assistants to a user's Codeforces account and live platform data, enabling problem discovery, submission review, rating tracking, contest planning, and friends or gym access through natural-language queries.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access Codeforces public data (users, contests, problems, etc.) via natural language or direct tool calls through Pipeworx gateway.55 npmMIT
- FlicenseAqualityCmaintenanceEnables coding agents to discover unsolved Codeforces practice problems, analyze tag performance, and inspect submissions, profiles, rating history, and upcoming contests through MCP-compatible clients.6-
- FlicenseNot gradedqualityBmaintenanceConnects Claude to the Codeforces public API, enabling retrieval of user submissions, profile info, rating history, contest standings, contest status, and contest lists through natural language.-
- AlicenseAqualityDmaintenanceA complete, all-in-one MCP server for Codeforces, enabling AI assistants to access user profiles, compare users, search problems, get practice recommendations, and more.83MIT
- AlicenseAqualityBmaintenanceEnables LLMs to fetch CodeChef profile data — ratings and rating history, contest results, submission activity, solved problems, and side-by-side user comparisons — as compact, typed JSON instead of raw HTML.648 npmMIT
TDQS
Scored across 17 tools
Most tools target distinct resources and actions, and descriptions clarify the boundaries between users, problems, submissions, and contests. A few pairs still have some overlap, especially search_problems vs list_problems for problemset discovery and get_contest_list vs get_upcoming_contests for contest listing.
The set uses consistent snake_case with verb_noun naming such as get_user_info, get_user_rating, search_problems, and list_problems. There are minor deviations like get_contest_list instead of list_contests, and get_recent_submissions vs get_user_submissions, but the pattern remains readable and predictable.
At 17 tools, the surface is slightly above the typical 3-15 range, but the breadth is justified by covering problems, users, submissions, contests, and diagnostics. Each tool has a plausible role, though a couple of pairs could potentially be consolidated.
The read-only Codeforces domain is well covered across problem discovery, user analytics, submission history, contest listings, standings, and rating changes. Minor gaps remain, such as fetching a specific submission or full problem statement, with the latter explicitly limited by the upstream API.