get_reset_timeline — Codex Reset MCP Tool Read-only
get_reset_timeline
(get reset timeline) is one of 3 tools on the
Codex Reset
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_reset_timeline from your client
- Claude Code Codex Reset get_reset_timeline run in your project directory
- Claude Desktop Codex Reset get_reset_timeline ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Codex Reset get_reset_timeline ~/.cursor/mcp.json
- VS Code Codex Reset get_reset_timeline .vscode/mcp.json
- Zed Codex Reset get_reset_timeline ~/.config/zed/settings.json
- Windsurf Codex Reset get_reset_timeline ~/.codeium/windsurf/mcp_config.json
- Cline Codex Reset get_reset_timeline ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Codex Reset get_reset_timeline ~/.gemini/settings.json
- Grok Codex Reset get_reset_timeline .mcp.json (in your project root)
- ChatGPT Codex Reset get_reset_timeline Settings → Connectors → Advanced → Developer mode
- Claude.ai Codex Reset get_reset_timeline Settings → Connectors → Add custom connector
- LangChain Codex Reset get_reset_timeline pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http codex-reset https://codex-reset.com/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.