codeforces-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| codeforces_search_problemsA | Find Codeforces problems by rating band and tags, easiest first. Set |
| codeforces_tag_performanceA | Rank a handle's problem tags by solve rate, weakest first. Computed from full submission history and deduplicated per problem, so grinding one problem twelve times counts once. Use it to decide what to practise: the lowest solve rates with a meaningful number of attempts are the real gaps. Codeforces exposes no endpoint for this. |
| codeforces_recent_submissionsA | List a handle's most recent submissions, newest first. Filter by |
| codeforces_user_profileA | Public profile for a Codeforces handle: rating, max rating, rank, organization. |
| codeforces_rating_historyA | Contest-by-contest rating changes for a handle, oldest first, with deltas. |
| codeforces_upcoming_contestsA | Contests that have not started yet, soonest first, with start time and duration. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct concern: problem search, tag-based performance analytics, recent submissions, user profile, rating history, and upcoming contests. There is no meaningful overlap or ambiguity between any pair of tools.
All names share the codeforces_ prefix and use snake_case, which makes them easy to predict and group. The pattern is not strictly verb_noun throughout, but the deviations are minor and do not hurt readability.
Six tools is a well-scoped size for a Codeforces companion server. Each tool covers a meaningful aspect of Codeforces usage without redundancy or bloat.
The surface covers the main Codeforces workflows: finding problems, analyzing weaknesses, reviewing submissions, checking profile progression, and seeing upcoming contests. A direct problem-statement or contest-problem listing tool would improve completeness, but the current set has no critical dead ends.