The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Codeforces MCP Server listing page.
Search official Codeforces problem metadata through a small MCP server.
Add the hosted server to your MCP configuration:
The endpoint accepts anonymous read requests. It does not need an API key, Cookie, or judge account.
Then ask:
| Tool | Purpose |
|---|---|
oj_capabilities | Report the available Codeforces read operations and transport. |
oj_health | Report service health and the latest official API observation. |
oj_search_problems | Search the official problemset by title, id, rating, or tag. |
codeforces_get_problem_metadata | Fetch official metadata by id, such as 158/A, 158A, or 158-A. |
Requires Node.js 22 or newer.
MCP client configuration from a source checkout:
Tagged GitHub releases attach a standalone npm tarball.
https://codeforces-mcp.ksrnyx.top/mcpio.github.ketherworks/codeforces, described by server.jsonoj_healthThis standalone release is generated from the reviewed Competitive Programming MCP source. The release package bundles the shared OJ contract implementation, so its runtime does not depend on unpublished workspace packages.
This project is unofficial and is not affiliated with or endorsed by Codeforces.
The server exposes no run or submit tool. It accepts no judge account credentials. See SECURITY.md for the security boundary and PROVENANCE.md for the canonical source revision.
Adapter source code is MIT licensed. Judge problem content and trademarks are not relicensed by this repository.