MCP server

ZeroWidth Ledger Official

ai.zerowidth/ledger

Checked 26 Oct 2026, 08:29 UTC · Connected to it and listed its tools

Log decisions with expectations, add evidence, and track metrics in Ledger.

Website

At a glance

Type

MCP server

Publisher

zerowidth.ai (verified by the MCP Registry)

Status

Working at last check

Tools

40

Token cost

About 16,664 tokens per request

Sets up in

Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok

Last checked

26 Oct 2026, 08:29 UTC

Connect it to your agent

Add to CursorAdd to VS CodeVS Code Insiders

Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.

Claude Code

claude mcp add --transport http ledger https://api.zerowidth.ai/mcp/x/ledger

Claude Desktop

Settings → Connectors → Add custom connector, and paste the URL.

Codex (config.toml)

[mcp_servers.ledger]
url = "https://api.zerowidth.ai/mcp/x/ledger"

Gemini CLI

{"mcpServers":{"ledger":{"httpUrl":"https://api.zerowidth.ai/mcp/x/ledger"}}}

Cursor

{"mcpServers":{"ledger":{"url":"https://api.zerowidth.ai/mcp/x/ledger"}}}

VS Code

{"servers":{"ledger":{"type":"http","url":"https://api.zerowidth.ai/mcp/x/ledger"}}}

Antigravity

agy mcp add ledger https://api.zerowidth.ai/mcp/x/ledger

ChatGPT

Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.

OpenAI API (Responses tools)

{"type":"mcp","server_label":"ledger","server_url":"https://api.zerowidth.ai/mcp/x/ledger","require_approval":"always"}

Grok (xAI API tools)

{"type":"mcp","server_label":"ledger","server_url":"https://api.zerowidth.ai/mcp/x/ledger"}

Tools

• ledger_entries_add_evidence ~486 tokens
  Records what happened against an open decision — a manual observation the user reports ('the pilot team says triage feels faster'), an implementation note, or a reference to a Caliper run. Evidence is what settlement later reads, so attach it as it arrives and cite it in the lesson. Metric readings
• ledger_entries_create ~1390 tokens
  Records a memory entry. Every entry is a TITLE (`summary`: one short plain sentence) over a BODY (`rationale`: the detail, markdown welcome) — never put the detail in the title. Three kinds: `decision` — a change being made now; PRE-REGISTRATION IS THE POINT, so `prediction` (what we expect) must be
• ledger_entries_draft ~1084 tokens
  Writes up to 50 entries as DRAFTS: proposals that stay out of the record until a person confirms each one in Ledger's Drafts view. Use it for entries you found rather than were told — decisions in meeting notes, or a team's past changes read from its tracker, pull requests or launch posts (set `from
• ledger_entries_get ~196 tokens
  One entry's full anatomy — the six fields, attached evidence (Caliper runs, measurements, observations), and the supersede chain (what replaced it, or what it replaced). Cite entry ids when telling the user about prior related decisions.
• ledger_entries_list ~530 tokens
  The workspace's memory: decisions (changes with pre-registered expectations), lessons (distilled beliefs), and observations (captured facts). CONSULT BEFORE ACTING — before proposing a flow change, prompt edit, or process decision, filter by the Compass page it touches (compassPageId) and check whet
• ledger_entries_retract ~286 tokens
  Takes an entry out of the curated ledger — THE remedy when you recorded something wrong (a decision that wasn't made, a duplicate, a fact the user corrects). Reversible from Ledger and fully audited, so it is safe to offer as soon as the user says 'that's not right'. Not for overturning a settled cl
• ledger_entries_settle ~413 tokens
  The ritual moment: evidence has landed, the expectation closes, the lesson is written. Only propose settlement when attached evidence actually answers the prediction — check `ledger_entries_get` first and cite the evidence in the lesson. `lesson` (what we now believe) is required and permanent; sett
• ledger_entries_update ~867 tokens
  Corrects an entry in place — its title (summary), body (rationale), the pre-registered prediction of an OPEN decision (null clears it), or its facet (filing category; editable even after settlement). Works on open decisions, and on lessons, observations, and beliefs (they carry no expectation, so fi
• ledger_feed_sources_list ~157 tokens
  The connected servers this workspace exposes to you, with the id a feed needs. Their tools appear to you namespaced as `ext__<name>__<tool>` — call one directly to see what it returns before proposing a feed. A server the workspace has switched off for you is not listed and cannot be fed from here.
• ledger_feeds_backfill ~308 tokens
  Run the same frozen instruction over a past range, so a metric has history instead of starting the day it was set up. Offer this whenever you create a feed — a chart with a year behind it is worth far more than one that begins today, and an expectation can be judged against what normal looked like.
• ledger_feeds_create ~537 tokens
  Freeze a tool call as a metric's standing source: it runs on the cadence you give and records what it finds, with no model involved. `metric` takes an id or a snake_case slug; an unknown slug starts tracking that metric. Confirm the mapping with ledger_feeds_preview first. Tell the user they can bac
• ledger_feeds_delete Deletes data · ~165 tokens
  Remove a feed. The readings it already wrote stay — the series is the record and outlives the instruction. Prefer pausing with ledger_feeds_update when the user might want it back. May return `needs_confirmation`.
• ledger_feeds_list ~174 tokens
  The standing instructions for how metrics' numbers arrive — which tool each one calls, how often, and how the last run went. Check before proposing a feed so you don't duplicate one, and consult when a user asks why a metric is stale: a feed with a failing last run is usually the answer.
• ledger_feeds_preview ~506 tokens
  Call a connected server's tool once and see what a mapping would pull out of the response — nothing is written and no feed is created. Send no `mapping` for a first look: you get a sample of the response plus the paths that hold numbers. Then send a mapping to confirm it finds the readings you expec
• ledger_feeds_run ~205 tokens
  Run a feed immediately over its own window and record what it finds. Use it right after creating one to prove the mapping works — a run that comes back `empty` names the path that missed, which is what you fix with ledger_feeds_update. Does not move the feed's schedule. Re-running is safe: readings
• ledger_feeds_update ~443 tokens
  Change a feed's arguments, mapping, cadence, or pause it. Reach for this when a feed's last run reports `empty` (the response shape moved, so the mapping needs a new path) or `error`. Changing the mapping changes what the number means, so say what you're changing and why. May return `needs_confirmat
• ledger_metric_presets_adopt ~278 tokens
  Creates the named presets as real metrics the workspace owns, tagged from the catalog. Safe to repeat: a preset the workspace already has comes back `already_present` rather than creating a second series, and a workspace's own renames and targets are never overwritten. Adopt only what the user agree
• ledger_metric_presets_list ~367 tokens
  Ready-made metrics a business can start tracking, each with a unit, a cadence, which direction is good, a business surface (facet), and cross-cutting tags. Reach for this when a workspace has few or no metrics, when someone asks what they should be measuring, or when a decision needs a number to set
• ledger_metric_starters_adopt ~286 tokens
  Creates a starter's metrics at their levels and links them. Pass `slugs` to keep only some of its metrics; links are made only where both ends exist. Safe to repeat and safe after a different starter: metrics the workspace already has are left as they are and get linked into the tree. Adopt only wha
• ledger_metric_starters_list ~208 tokens
  Starter trees by shape of business or team (subscription software, services firm, online store, sales team, service operation). Each lists its metrics with a level (outcome / driver / activity) and the links between them (which number moves which). Reach for this before ledger_metric_presets_list wh
• ledger_metrics_archive ~286 tokens
  Takes a metric out of the gallery (`archived: true`) or puts it back (`false`). Readings stay, and entries that settled against it still read correctly — this is the cleanup for a metric minted once and abandoned, or one the workspace stopped watching. `metricId` accepts the id or slug from ledger_m
• ledger_metrics_create ~600 tokens
  Create a metric — a number the workspace watches (triage time, weekly signups, cost per run). Check ledger_metrics_list first; names are unique per workspace. When a user says they want to track or measure something, offer this. May return `needs_confirmation`.
• ledger_metrics_get ~481 tokens
  One metric's definition (unit, kind, direction, target, cadence) plus its readings newest first and the open decisions bound to it. Use before answering 'how is X trending?' or before recording a reading against it. `metricId` accepts the id or the snake_case slug from ledger_metrics_list. For an ev
• ledger_metrics_list ~161 tokens
  The numbers the workspace watches — each with unit, latest reading, and how many open decisions are bound to it. Consult when a user mentions a number that sounds like a tracked metric, and before recording a reading.
• ledger_metrics_record_reading ~692 tokens
  Record one observation of a tracked metric. `metricId` accepts a metric id OR its snake_case slug from ledger_metrics_list; an unknown one is a not_found error — check ledger_metrics_list, create it with ledger_metrics_create, or pass `createIfMissing: true` to mint a "measure" metric at that slug i
• ledger_metrics_update ~880 tokens
  Corrects a metric's name, unit, description, kind (measure / event), direction (which way is good), target, cadence, icon, level, or the metrics it drives (its place in the metric tree). Readings are untouched. Only what you pass changes. The slug is not editable here — external writers address metr
• ledger_plan_add ~604 tokens
  Adds a plan item to an OPEN decision (the work that carries it out: a post, a launch step, an email). Omit entryId for a standalone date (a holiday, an event you're only watching). Items are all-day unless you pass startTime with timeZone (and optionally endTime), for a webinar, a scheduled post, or
• ledger_plan_delete Deletes data · ~230 tokens
  Removes one plan item while its decision is open, for an item added by mistake or work that's no longer planned. If the work was planned and then dropped, prefer ledger_plan_update with status 'skipped' so settlement can see it. Fails with conflict once the decision is settled. May return `needs_con
• ledger_plan_list ~323 tokens
  Pass `entryId` for one decision's plan items, or `from` + `to` (YYYY-MM-DD, at most about a year apart) for the calendar: decision spans (recorded day → expectation deadline) plus every dated item inside the window, including standalone dates with no decision. Filter the calendar by `ownerUserId` to
• ledger_plan_update ~462 tokens
  Edits one plan item while its decision is open: move it (dueOn), rename it, change the owner (null clears), attach the link, or set status (planned | done | skipped). Mark done only when the user says it shipped; a link alone doesn't mean done. Fails with conflict once the decision is settled. May r

Browse

• Website monitoring
• Converting to Markdown
• Online shops

Related MCP servers

• ZeroWidth Compass
  Read and update your Compass map: pages, changes, opportunities and interviews.
• ZeroWidth Prism
  Explore ideas in Prism fields, run studies, and read research findings.
• Peopleanalyst Discovery
  PeopleAnalyst's free people-analytics feeds: answers, tools, evidence, story and scene catalogs.
• NoiseFloor — market attention and evidence checks
  Offline market diagnostics, news repetition, data coverage and statistical checks for AI agents.
• ZeroWidth Napkin
  Draw boards, write docs and sheets, and build decks with your brand in Napkin.
• Worthune Verified Financial Models
  61 verified financial models and a household planning engine: 20 MCP tools, 6 keyless, specs cited.
• Agi Scorecard
  8 graded AGI-2027 predictions, the 0-100 Thesis Tracker, and a public market-call ledger. Free.
• The Cure Protocol
  Agent research API for 15 disease areas, plus a T1D cure lab, sourced evidence ledger and models.

Badge for your README

[![AptLynx](https://aptlynx.net/badge/ai.zerowidth/ledger.svg)](https://aptlynx.net/servers/ai.zerowidth/ledger)

Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents