list_organisations
List accounting organisations
List the accounting organisations (Xero, Sage, Reckon, or QuickBooks) connected to the authenticated Boxkite account.
Takes no parameters.

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 5, 2026
Read-only backup and export of Xero accounting data: organisations, exports, manifests, downloads.
Local bridge to the hosted Boxkite service that lets an assistant list connected accounting organisations and run read-only exports of their data.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
ledgerbackup is a small local bridge to the hosted Boxkite MCP server, which backs up and exports accounting data from the organisations connected to your Boxkite account (Xero, Sage, Reckon, or QuickBooks). It lists those organisations, starts a read-only export of one organisation's data, and then tracks that export through its status, manifest and file-to-object mapping until a signed download URL for the finished ZIP is available.
The bridge keeps no accounting data of its own. It serves the upstream server's tool list locally, exactly as captured from the live endpoint, and forwards each tool call upstream, returning the result untouched.
list_organisations — list the accounting
organisations connected to the authenticated
Boxkite account. No arguments.start_export — start a read-only export of one
organisation's data. Required: organisationId
(from list_organisations). Per the upstream
description, an export costs $39 per organisation:
when payment is outstanding the response is status
awaiting_payment with a Stripe checkout URL, and
repeat calls return the existing export rather than
creating or charging for a second one. A typical
export runs for hours.list_exports — list one-off exports, newest
first, optionally filtered by organisationId.
Side-effect free: it never starts an export or
charges anything.get_export_status — report one export's state
(queued | running | ready | failed), its progress,
and when to poll again. Required: exportId.get_export_manifest — see what an in-progress
export contains so far, paged via fileOffset and
fileLimit. Required: exportId.get_export_mapping — for an in-progress export,
map each discovered file to the accounting object
it represents, paged the same way. Required:
exportId.get_download_url — return a short-lived signed
URL for the finished export ZIP, valid within the
export's 7-day retention window. Required:
exportId.BOXKITE_MCP_URL (optional) — override the
upstream endpoint. Defaults to
https://app.getboxkite.com/mcp. (The override
hook is this rebuild's own labelled reconstruction.)BOXKITE_API_KEY (optional) — when set, every
upstream request carries an
X-API-Key: <key> header with your Boxkite API
key. When it is not set, no key header is sent.
No Authorization header is ever sent. (This
forwarding is also a labelled reconstruction; the
original surface was captured keyless.)On the first tool call the client opens a streamable
HTTP session with the upstream: a JSON-RPC
initialize request (protocolVersion 2025-03-26,
clientInfo name ledgerbackup), then a
notifications/initialized notification, then the
tools/call request carrying the caller's arguments
unchanged. When the upstream answers initialize
with an Mcp-Session-Id header, that value rides on
every later request of the session, which is reused
for the life of the process. Replies may arrive as
plain JSON or as server-sent events; both are read.
Successful upstream results pass through verbatim,
including any isError flag the upstream sets.
Failures — a JSON-RPC error, a non-2xx status, an
unreadable response, or a request that cannot be
completed — come back as an isError result whose
text starts with ledgerbackup error: (this
rendering is this rebuild's own labelled
reconstruction).
Each tool is also a subcommand taking one JSON argument string:
Exit codes: 0 on success, 1 on an isError
result, 2 on a usage error.
MCP client config:
The container's default command is mcp, so the
first form is a stdio MCP server; any other arguments
reach the CLI normally.
The test suite runs entirely against a stubbed JSON-RPC upstream — no live network calls.
MIT — see LICENSE.
Source: README.md at commit 9b4133b
List accounting organisations
List the accounting organisations (Xero, Sage, Reckon, or QuickBooks) connected to the authenticated Boxkite account.
Takes no parameters.
Start a one-off accounting data export
Starts a read-only export of one accounting organisation's data (Xero, Sage, Reckon, or QuickBooks). Costs $39 per organisation: when payment is outstanding the response is status 'awaiting_payment' with a Stripe checkoutUrl for the user to complete in a browser, and the export begins once that payment settles. This is not a status endpoint: it reports only the state at creation, and repeat calls return the existing export for that organisation rather than creating or charging for a second one. Export progress is reported by get_export_status, and newly created exports appear in list_exports. A typical export runs for hours, and pauses whenever it meets a provider rate limit or Boxkite's egress budget — anything from under a minute to the next UTC day. get_export_status reports when it resumes.
organisationIdrequiredList exports
List one-off exports (newest first), optionally for one organisation. Use this to find an export after payment and to poll its status until it is 'ready'. Side-effect free: it never starts a new export or charges anything. Each entry carries progress, parkedUntil and pollAfterSeconds.
organisationIdGet export status
Reports the state of one export: status (queued | running | ready | failed) and whether its download is available yet. Also returns progress {discovered, transferred, percent}; parkedUntil; and pollAfterSeconds, the interval after which this status is expected to have changed. A large export runs for hours, so pollAfterSeconds can be a long interval. parkedUntil is a timestamp, present whenever work on the organisation is paused and expected to resume. How long varies by cause and is not worth guessing at: hitting Xero's per-minute limit pauses for under a minute, approaching its daily quota pauses for about an hour, and exhausting the daily quota or Boxkite's own egress budget pauses until the next UTC day. Wait until the timestamp (or pollAfterSeconds, which already accounts for it) rather than describing a cause to the user.
exportIdrequiredGet export manifest
See what an IN-PROGRESS export contains so far (entities included, per-entity record/file counts, and per-file checksums), growing as discovery and downloading proceed. The per-file list is paged: check filesPage.hasMore and pass fileOffset to walk it. Once the export finishes, this returns status 'complete' with a pointer instead of a list, because the full manifest travels inside the ZIP as manifest.json: get a download URL, then read manifest.json from the archive.
exportIdrequiredfileLimitfileOffsetGet export file→object mapping
For an IN-PROGRESS export, get the mapping of each file discovered so far to the accounting object it represents or is attached to (e.g. which invoice a receipt PDF belongs to). Paged (default 200 files, max 500): check filesPage.hasMore and pass fileOffset for the next page; the `objects` map covers only the files on the current page. Once the export finishes, this returns status 'complete' with a pointer instead: the full mapping ships under Info/ inside the ZIP, so download the archive and read Info/files.json from it.
exportIdrequiredfileLimitfileOffsetGet export download URL
Returns a short-lived signed URL for the export ZIP, valid within the export's 7-day retention window, along with byteSize (the archive's size in bytes, null if unavailable) and fileCount. These archives range from a few MB to several GB. The archive contains the exported files plus manifest.json (every file with its sha256) and Info/ (the file-to-Xero-object mapping).
exportIdrequired90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
npx @reneturcios/ledgerbackup list_organisationsnpx @reneturcios/ledgerbackup start_export '{"organisationId":"org-123"}'npx @reneturcios/ledgerbackup get_export_status '{"exportId":"exp-9"}'npx @reneturcios/ledgerbackup get_download_url '{"exportId":"exp-9"}'npx @reneturcios/ledgerbackup --versionnpx -y @reneturcios/ledgerbackup mcp{ "mcpServers": { "ledgerbackup": { "command": "npx", "args": ["-y", "@reneturcios/ledgerbackup", "mcp"] } }}docker run -i ghcr.io/cloudcorprecords/ledgerbackupdocker run --rm ghcr.io/cloudcorprecords/ledgerbackup --versionnpm installnpm run buildnpm testnpm run dev