MCP.Market

Usage Planner MCP server

by ItsOdeLeo·io.github.ItsOdeLeo/usage-planner·v0.2.7·3 stars

Plan OpenAI Codex usage from local quota, banked resets and extra-reset forecasts.

A85/100grade A
What users say
No reviews yet
Be the first
Safety scan
A85/100

not scanned yet

Adoption
Growing

3 stars

Reviews

Write one

Nobody has reviewed Usage Planner yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Usage Planner tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Usage Planner compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 73% of 4,460 AI and agents servers
GitHub stars
3
more than 75% of 2,711 AI and agents servers

Release history: 2 versions in the registry since 2026-10-23, latest 2026-10-24, typically one every 1 day.

Install Usage Planner in Claude Code, Cursor or VS Code

Runs npx -y usage-planner on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add usage-planner -- npx -y usage-planner
Add to Cursor

What the publisher says

From the Usage Planner repository's README, as published. We do not edit it. Read it on GitHub

Usage Planner — Codex quota & reset planner

Know how much Codex to use today.

If you find it useful, a ⭐ star helps more people find it.

Runs in your browser · no sign-in · or ask Codex with the plugin

English · 中文简介

Usage Planner (formerly Codex4ever) is a planner for your OpenAI Codex weekly quota. It shows when your quota runs out at your current pace, whether a predicted extra reset is likely to arrive first, and when a banked reset is worth redeeming.

Unofficial; not affiliated with OpenAI. MIT licensed.

Pick a strategy

Ask once in Codex and the planner opens beside the chat. Pick a strategy and the plan changes: daily usage, refills and run-out points.

What it does

  • Timeline of your next two weeks — daily usage, remaining quota, run-out points, outages, normal refreshes and banked-reset uses, one column per day.
  • Extra-reset forecast — the chance of an automatic reset in the next 48 hours, the likely window, and a second reset conditioned on the first, built from public reset history and Tibo's public posts.
  • Five strategies — Keep pace (your current pace: see when quota runs out), Keep available, Use it all (empty quota just before the next refill), Weekdays only, Weekend focus.
  • Codex plugin — reads your local, signed-in quota and banked resets, plans in the conversation, and opens the same visual planner.

How it plans

  • A predicted reset is counted only when it is at least 60% likely before the refresh in effect, and it is placed at a conservative time (where it has most probably already happened), not at its single most likely hour. You can switch the count to 0, 1 or 2 on the timeline.
  • Every refill restarts the seven-day window — a banked reset, an extra reset or the normal refresh.
  • Banked resets: extras cover outages, earliest expiry first; the last one is kept for a real outage (24 h or more), and a bank about to expire can be used rather than wasted.
  • One rule everywhere: the website, the plugin page and the plugin's MCP tools always give the same plan for the same inputs.

The forecast is an uncalibrated model estimate, not a promise. Usage Planner never redeems a reset or spends credits for you.

Use it

Codex plugin (Node.js 20+ and a signed-in Codex app or CLI):

codex plugin marketplace add ItsOdeLeo/usage-planner
codex plugin add usage-planner@usage-planner

Start a new Codex chat and ask: "Open quota planning." Reading your quota is local and read-only; no separate API key is needed.

Other MCP clients (Claude Code, Claude Desktop, Cursor and others): the same server is on npm as usage-planner and in the MCP Registry as io.github.ItsOdeLeo/usage-planner. Reading your quota still needs a signed-in Codex CLI on the same machine.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Usage Planner: common questions

Is Usage Planner MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the Usage Planner safety report
How do I install Usage Planner?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Usage Planner need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Usage Planner maintained?
The last commit was 12 days ago (2026-10-23). The latest release is v0.2.7.
What can I use instead of Usage Planner?
Servers from other publishers that do the same job: three.ws Billing MCP server, Agent-Native Plan MCP server and SuperCompress MCP server.
How does Usage Planner compare with other AI and agents MCP servers?
safety score 85/100 (higher than 73% of 4,460 AI and agents servers); github stars 3 (more than 75% of 2,711 AI and agents servers). Full comparison.

Alternatives to Usage Planner

Same job from other publishers: the closest match first, then the best rated.

  • three.ws Billing
    An agent's account economics — plan quotas, metered usage, invoices, receipts, and earnings.
    B
  • Agent-Native Plan
    Structured visual plans and PR recaps with diagrams, prototypes, annotations, and sharing
    A
  • SuperCompress
    Compress coding-agent context ~64%. Hosted Neural Keep MCP for Cursor/Claude/Codex.
    B
  • OpenWorkProof
    Verifiable agent evidence; opt-in Codex guard and reference SOC alert review.
    A
  • freellmpool
    OpenAI-compatible MCP gateway cataloging 22 LLM providers, with routing, failover, and tools.
    A