Skip to main content
Glama
README.md
<div align="center">
  <img src="docs/tallybook-mark.svg" alt="Tallybook logo" width="104" />
  <h1>Tallybook</h1>
  <p><strong>Prices every Claude Code and Codex session on your disk, shows what each agent cost over any period, and tells you in plain English what would have been cheaper.</strong></p>
  <p>
    <a href="https://github.com/magna-nz/tallybook/actions/workflows/ci.yml"><img src="https://github.com/magna-nz/tallybook/actions/workflows/ci.yml/badge.svg?branch=main" alt="CI" /></a>
    <a href="https://github.com/magna-nz/tallybook/releases/latest"><img src="https://img.shields.io/github/v/release/magna-nz/tallybook?sort=semver&label=release" alt="Latest release" /></a>
    <a href="https://modelcontextprotocol.io/"><img src="https://img.shields.io/badge/MCP-server-005FBA" alt="MCP server" /></a>
    <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-yellow.svg" alt="MIT License" /></a>
    <a href="https://glama.ai/mcp/servers/magna-nz/tallybook"><img src="https://glama.ai/mcp/servers/magna-nz/tallybook/badges/score.svg?v=2" alt="Glama Quality" /></a>
  </p>
  <p><a href="https://magna-nz.github.io/tallybook/">Documentation</a></p>
</div>

<br />

No proxy, no API key, nothing leaves your machine. Run it as a CLI, open the same report in your
browser with `tallybook --serve`, or add `tallybook-mcp` to Claude Code or Codex and ask the agent
itself what it's spending and what would be cheaper.

<div align="center">
  <img src="docs/web-ui.gif" alt="tallybook --serve: the same report in your browser" width="820" />
  <br />
  <sub><strong>In your browser</strong> · <code>tallybook --serve</code></sub>
  <br /><br />
  <img src="docs/cli.gif" alt="tallybook in the terminal: the report, a week-on-week comparison, and spend by sub-agent" width="820" />
  <br />
  <sub><strong>In your terminal</strong> · <code>tallybook</code></sub>
</div>

<br />

More in the [documentation](https://magna-nz.github.io/tallybook/).

## Install

```sh
brew install --cask magna-nz/tap/tallybook
```

Also available via `go install github.com/magna-nz/tallybook/cmd/tallybook@latest`, or as a
[release download](https://github.com/magna-nz/tallybook/releases/latest). Works on macOS, Linux
and Windows.

Add the MCP server so your agent can check its own spend mid-session — `tallybook-mcp` ships
alongside `tallybook`, so no separate install:

```sh
claude mcp add tallybook -- tallybook-mcp   # Claude Code
```

For Codex, add it to `~/.codex/config.toml`:

```toml
[mcp_servers.tallybook]
command = "tallybook-mcp"
```

## Use

```sh
tallybook                         # this period's report: the five biggest findings
tallybook --serve                 # the same report, findings and sessions in your browser, on localhost
tallybook findings                # every finding, grouped by what kind of change it asks for
tallybook --since 7d --compare    # this week against last week: spend, sessions, cache hit rate
tallybook finding 1               # finding #1 in full: what happened, why, what to change
tallybook finding 1 --evidence    # the same, with the sessions behind it
tallybook finding 1 --patch       # finding #1's fix, as an applyable diff
tallybook agents                  # spend by sub-agent type, with the model and effort each ran at
tallybook sessions --sort cost    # sessions ranked by what they cost
tallybook changes                 # did a past model swap actually save money?
tallybook setup hook              # record sessions automatically as they end
```

## Docs

The command reference, the MCP server's tools, configuration, and the privacy model live on the
**[documentation site](https://magna-nz.github.io/tallybook/)**.

## License

MIT

TDQS

A3.8/5.0

Scored across 8 tools

Disambiguation4/5

Most tools target distinct facets: report (aggregate), sessions (list), session (single), agents (sub-agent breakdown), changes (model-change points), finding (one finding), prices, refresh. The main risk is report vs sessions vs agents overlapping in cost-summary territory, and session vs sessions differing only by plural, but descriptions clearly separate them.

Naming Consistency4/5

All names are single lowercase nouns (agents, changes, finding, prices, refresh, report, session, sessions), so the convention is applied consistently. The only weakness is session/sessions and agents/sessions reading similarly, which slightly hurts predictability.

Tool Count5/5

Eight tools is well-scoped for a cost-tracking server, with each tool mapping to a clear function (scan, price table, aggregate report, listing, drill-down, sub-agent detail, model-change tracking, findings). Nothing appears redundant or padded.

Completeness5/5

The surface covers the full lifecycle: refresh to ingest data, prices for computation basis, report/sessions/agents for aggregate and sub-agent views, session for turn-level drill-down, changes for model change comparisons, and finding for full advice with evidence. No obvious gaps or dead ends for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues