mcpField
S

seatledger

Local

About seatledger

Local ledger of Claude Code and Codex tokens, API-equivalent cost, limits and token-rate changes.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"agentwares-seatledger": {
"command": "npx",
"args": [
"-y",
"seatledger"
],
"env": {
"CLAUDE_CONFIG_DIR": "<CLAUDE_CONFIG_DIR>",
"CODEX_HOME": "<CODEX_HOME>",
"SEATLEDGER_HOME": "<SEATLEDGER_HOME>",
"SEATLEDGER_KEY": "<SEATLEDGER_KEY>"
}
}
}
}
Run commandnpx -y seatledger
Environment variables to set
CLAUDE_CONFIG_DIRClaude Code's config directory, if not ~/.claude; transcripts are read from its projects/ folder
CODEX_HOMECodex's home directory, if not ~/.codex; rollouts are read from its sessions/ folder
SEATLEDGER_HOMEWhere seatledger keeps your limits and its cache of counts (default ~/.seatledger)
SEATLEDGER_KEYSecretTeam ledger push key for seatledger_team_summary, if not saved by `seatledger team join` or `team create`

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmseatledger0.3.0

Tools

4

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
sincestringNoStart of the range: a local date (`2026-09-01`) or a span back from today (`30d`, `12w`). Omitted with `group_by` set: 30d.
clientenumNoOnly this coding-agent client: `claude-code` (Claude Code transcripts) or `codex` (Codex CLI rollouts). Omitted: both.claude-code | codex
group_byenumNoGroup the range by local `day`, `project` (working-directory folder name), `model` or `client`. Omitted with `since` set: day.day | project | model | client

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.