Back to directory

Codex Usage Tracker

A local-first MCP tool and dashboard for investigating how Codex CLI work consumes tokens, time, tools, allowance, credits and cost, and for spotting caching and thread patterns.

Codex Usage Tracker

Codex Usage Tracker turns local Codex session metadata into exact, bounded facts an agent or developer can explore and explain: session, turn, tool call, resource, allowance, token, credit and cost data, surfaced through a six-tool MCP interface, an Evidence Console, and a local SQLite kernel. Version 0.28.0 is the current public release of this design.

The project's next direction is a cleaner, agent-first kernel rather than a larger dashboard: fast setup covering anywhere from the last 24 hours to all-time history, incremental reuse on later runs, compact named queries and stable evidence selectors, and agent-owned interpretation instead of server-written narrative findings; the 0.28 code stays available as a frozen reference during that rewrite. It installs with pipx and registers as a Codex plugin marketplace entry. Development uses synthetic fixtures only; real Codex logs, prompts, outputs or credentials are never committed or shared.

More in MCP servers

See all 734
  • Light Cloud

    light-cloud.com

    A hosting platform that deploys a static site, a container, or a managed Postgres database straight from a GitHub, GitLab, or Bitbucket push, with a preview URL for every branch and an MCP server for deploying from Claude Code.

  • ForensicDbg

    forensicdbg.com

    A post-mortem debugger for native Windows x86 and x64 crashes, with an MCP interface so AI tools can consume crash-dump analysis directly.

  • Karada.ai

    karada.ai

    A CI/CD platform that auto-compiles existing APIs into Go MCP servers, attaches composable middleware, and exposes them through one gateway usable from Cursor, Claude Code, and Windsurf.