oj_search_problems — AtCoder MCP Server MCP Tool
oj_search_problems
(oj search problems) is one of 4 tools on the
AtCoder MCP Server
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call oj_search_problems from your client
- Claude Code AtCoder MCP Server oj_search_problems run in your project directory
- Claude Desktop AtCoder MCP Server oj_search_problems ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AtCoder MCP Server oj_search_problems ~/.cursor/mcp.json
- VS Code AtCoder MCP Server oj_search_problems .vscode/mcp.json
- Zed AtCoder MCP Server oj_search_problems ~/.config/zed/settings.json
- Windsurf AtCoder MCP Server oj_search_problems ~/.codeium/windsurf/mcp_config.json
- Cline AtCoder MCP Server oj_search_problems ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AtCoder MCP Server oj_search_problems ~/.gemini/settings.json
- Grok AtCoder MCP Server oj_search_problems .mcp.json (in your project root)
- ChatGPT AtCoder MCP Server oj_search_problems Settings → Connectors → Advanced → Developer mode
- Claude.ai AtCoder MCP Server oj_search_problems Settings → Connectors → Add custom connector
- LangChain AtCoder MCP Server oj_search_problems pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http atcoder https://api.ksrnyx.top/oj-mcp/atcoder/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.