Skip to main content
Glama

Server Details

AI bookkeeper for Swiss small companies: books invoices, reconciles the bank, keeps VAT current.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

B3.1/5.0

Scored across 51 tools

Disambiguation4/5

Most tools target a distinct resource+action, and the descriptions actively disambiguate the tricky pairs (upload_document vs upload_intake, list_gl_periods vs list_gl_vat_periods, gl_trial_balance vs get_financial_statements). The residual ambiguity is the several parallel 'accept/reconcile' doors (accept_autopost_decision, book_documents_act, reconcile_bank_act) and the five upload paths, which a careless agent could still pick wrongly.

Naming Consistency4/5

Everything is snake_case and most names follow verb_noun (get_bank_entry, list_gl_accounts, create_gl_journal_entry, reverse_gl_journal_entry). Deviations are the noun-only names (customer_statement, gl_trial_balance, entry_candidates, onboarding_guide, zeno_info) and the odd *_act suffix on book_documents_act / reconcile_bank_act, but the convention remains readable.

Tool Count2/5

51 listed tools is a heavy surface, well above the comfortable 3-15 range, even for a full accounting platform spanning GL, AR/AP, banking, VAT, payroll, documents and auth. The find_operations/describe_operations/call_operation layer already exposes several hundred more operations, so the large static list adds selection cost without adding reach.

Completeness4/5

Coverage is deep across the accounting lifecycle: ingest/upload, document booking, journal entry create/post/reverse, bank reconciliation and settlement, AR reads, aging/statement, payroll import, plus auth and onboarding. Gaps exist in the listed tier (no delete-draft, no create_ar_invoice, no update for most entities, no reconciliation completeness call), but the call_operation escape hatch makes them reachable rather than dead ends.

Available Tools

51 tools
accept_autopost_decisionAInspect

One-click accept of a held decision (accountant) — posts the AI's proposal.

A person's accept overrides the soft guardrails. An agent's is refused (403) unless the row is agent_acceptable or an expense receipt. Closed period, sealed year, unknown account: 409/422. The row flips held → posted (again: 409); accepted_by_kind records the channel (mcp over MCP).

Optional body: expense:receipt:item: needs employee_id + category_id; autopost:capitalize: needs fixed_asset_category_id when the hold has none, and needs_split_source a reclassify_from_account_code.

Inputs: company_id (required), decision_id (required), body.

attach_cash_entry_receiptBInspect

Attach a receipt to a posted cash-book entry: a new file (file_base64, the raw bytes, base64) OR an existing document's item_id, exactly one. override_duplicate only after a duplicate refusal you checked.

Inputs: entry_id (required), company_id (required), register_id (required), item_id, +3 more.

attach_claim_receiptAInspect

Attach a receipt to an expense-claim line: a new file (file_base64, the raw bytes, base64) OR an existing document's item_id, exactly one; repeat that item_id as receipt_from_upload when ingest_expense_receipt returned it. override_duplicate only after a duplicate refusal you checked.

Inputs: line_no (required), claim_id (required), company_id (required), item_id, +4 more.

book_documents_actAInspect

One action on one open document (ZEN-2): an action its row offers, with its version.

accept posts the held proposal; reject closes it unposted (a person books the document); keep, reanalyze, mark_irrelevant, delete; skip / unskip leave it to a person. All but accept and unskip need a reason. Recorded with your user; an agent decides a hold only where the owner allowed it. Returns the new status.

On this MCP surface a null argument means "not provided": it is dropped before the request is sent, exactly as if the field were omitted.

Inputs: action (required), version (required), company_id (required), decision_id (required), +1 more.

call_operationAInspect

Run any operation by name — the ones in your tool list and the unlisted ones alike.

name is an operation name from find_operations; arguments is the object described by describe_operations (omit it for an operation that takes none). The result, and any error, are exactly what calling the operation directly would give you.

Inputs: name (required), arguments.

collect_api_keyAInspect

Collect the key once the user has approved.

status is one of:

  • pending — nobody has approved yet, or (with throttled: true) we were rate-limited and learned nothing. Wait poll_interval_seconds, then call again — every answer carries it. Do not ask the user to tell you when they are done: you cannot detect it any other way, and handing the wait back to the user is how these sessions die.

  • ready — api_key is the credential. Follow the note that comes with it before anything else: the key does nothing until the client's configuration holds it, and calling again issues nothing. scope says what it can reach (onboarding, company or full) and company_id which company, if any. When scope is onboarding the user has no company yet and this key exists to make one: call onboarding_guide next — it needs no key, so read it while the user installs this one. It is the only place that says which documents to ask them for, and asking for them all at once is the difference between one conversation and seven.

  • collected — this request already issued its key and nothing new was issued. Follow the note.

  • denied — stop. Do not start another request; a human refused it ("that was not me"). Raising a second one is how a refusal turns into a prompt the user has to refuse repeatedly.

  • expired — the request timed out. Do not simply open another one, and what to do depends on which door you opened, which only you know. request_api_key: ask whether they saw the approval page, and call it again if they want to retry. start_signup: they may have finished registering in the browser meanwhile, in which case they now HAVE an account and request_api_key is the path — ask. If they did not, tell them plainly that it timed out; starting another signup without asking is how a refusal turns into a prompt they have to refuse repeatedly.

A pending answer is a success, not an error; it is deliberately not an error status, because an error would be read as "do not retry" and retrying is the entire protocol. A rate limit mid-wait is reported the same way, with throttled: true and a longer poll_interval_seconds — slow down, do not stop.

Inputs: claim_token (required).

create_gl_journal_entryAInspect

Create a draft journal entry by hand — accountant. It carries NO source document unless you name one.

Only the pipeline paths stamp source_ref_type/source_ref_id (an ingested document is 'item'), so by default a booking made here cannot be traced back to what justified it. document_id is the retrofit: name an existing gl_document (create one with POST …/gl/documents) and it is attached as the entry's source document, so the entry is not evidence-less. The same attach is available afterwards at POST …/gl/journal-entries/{id}/documents — including on a posted entry.

Use it for bookings with genuinely no document behind them — reclassifications, provisions, accruals, year-end adjustments. Do not transcribe a document into it and then attach the file — that files the evidence beside a booking nobody derived from it. Each of these has a door that keeps the evidence attached:

  • an invoice, receipt or statement → ingest the file (POST …/uploads/ or …/intake), then accept what the coder proposes (…/autopost-decisions);

  • an already-ingested item → POST …/gl/items/{item_id}/coding;

  • a bank movement with no document → POST /bank-entries/{entry_id}/manual-coding;

  • opening balances → POST …/opening-entries and post the proposal.

auto_reverse_date arms the entry as a one-shot accrual (ZCT-527): once posted, the auto-reversal executor reverses it in full on/after that date. It must be after posting_date (422 otherwise), and it can only be set while the entry is a draft — on the create here or on the PUT replace.

Drafts do not touch the books until …/post. See doc/pipeline.md §"Accounting".

On this MCP surface a null argument means "not provided": it is dropped before the request is sent, exactly as if the field were omitted.

Inputs: lines (required), period_id (required), company_id (required), posting_date (required), +7 more.

customer_statementBInspect

One customer's open items + totals (the aging row's drill-down).

as_of mirrors GET …/ar/aging — set, it reconstructs the items open at that date so the statement agrees with a historical aging report.

Inputs: company_id (required), counterparty_id (required), as_of.

describe_operationsAInspect

Get the full argument schema for operations found via find_operations.

Returns each operation's description and JSON-Schema arguments — everything a listed tool would have shown you.

include_output_schema is the ONLY way to obtain an operation's result shape: tools/list publishes no output schema for any operation, listed or not (they are 67 % of the payload, and a schema describing a result is not what you need to choose a tool). Ask for it when you must know the shape in advance; the result itself comes back as JSON either way, so usually you do not.

Up to 10 operations per call; anything beyond that is reported in omitted rather than dropped.

Inputs: names (required), include_output_schema.

entry_candidatesCInspect

Documents, booked invoices, open items one movement may pay; link one, then settle_entry.

Inputs: entry_id (required).

find_operationsAInspect

Search EVERY operation this server offers, including the ones not in your tool list.

The tool list you can see holds only the common operations. Several hundred more — payroll, VAT returns, year-end close, fixed assets, expenses, cash book, settings, integrations, onboarding — are available but unlisted, and this is how you find them. Search here before concluding that Zeno cannot do something.

Call with no arguments to browse the catalogue of areas (tags) with their operation counts; with tag to list one area; with query to search by keyword. Every word contributes and matching all of them doubles the score, so extra words widen the search rather than narrowing it — the AND-then-fall-back- to-OR behaviour this said before was removed in ef47aa9ab. A word matching an operation's name counts for far more than one found in its description, so prefer the noun you are looking for over a sentence.

limit is capped at 100 per call; when more matched, next_offset gives the offset that returns the following page, so an area of any size can be read in full. Paging is stable — the ranking is deterministic and the registry is fixed at startup, so no operation is dropped or repeated between pages.

Pass a promising name to describe_operations for its arguments, then run it with call_operation.

Inputs: tag, limit, query, offset.

get_ar_invoiceAInspect

One authored outgoing invoice with its lines (CompanyMember read).

Carries the header (customer, dates, currency, discounts), every line with its computed net_amount/vat_amount/gross_amount, the document totals, and the lifecycle: status (draft → issued → cancelled), document_no (assigned at issue — null on a draft), commercial_document_id / snapshot_document_id (the booked document and the frozen PDF), plus the derived payment_status and open_amount read from the linked open item.

This is the authored arm only. A receivable that arrived as an ingested document is an item, not an ar_invoice; the two arms are listed together by GET …/ar/receivables. Use GET …/ar/invoices/{invoice_id}/related for the journal entry, the settling bank transactions and the credit-note chain.

Inputs: company_id (required), invoice_id (required).

get_bank_entryCInspect

One bank movement with its reconciliation state and links.

Inputs: entry_id (required).

get_bank_statusAInspect

Composed bank snapshot — "is my banking up to date?" (CompanyMember). "Reconciled" means entries matched, NOT ledger = statement balance (the close check BANK_BALANCE_DOES_NOT_TIE_OUT compares that).

Per-account entry-status and in_suspense counts, each account's latest closing balance, and the company-level cumulative GL Suspense balance. Non-zero suspense blocks a clean VAT close.

Read-only. Gaps come from the account's full history: coverage windows are merged and every internal hole reported (ZCT-509), so a run of missing statements is ONE gap. Not period-scoped; use …/reconciliation/completeness per month. period_gaps caps at 10/account, period_gap_count stays exact — HOLES, not missing months. Explicit non-member company_id → 403.

Inputs: company_id (required).

get_companyBInspect

Get one company (jwt, scoped). 403 for a non-member non-admin, 404 if absent.

Inputs: company_id (required).

get_financial_statementsAInspect

Computed balance sheet + P&L for a fiscal year, from the journal (CompanyMember).

Aggregates every posted GL journal line whose posting date falls in the fiscal year's window, classifies each account against the chart of accounts, and reports problems (unbalanced trial balance, unclassified accounts, year-not-opened, mixed currency). Read-only and distinct from the uploaded balance-sheet snapshots (GET .../balance-sheets): nothing here reads a snapshot. fiscal_year optional → the latest FY with journal data. month (YYYY-MM, inside the FY — 422 otherwise) narrows the statement to one month: the balance sheet stays cumulative (as of month end, YTD equity fold) while the P&L + cash flow cover that month's flows. Explicit non-member company_id → 403.

The cut: posting_date inside the fiscal year's own window (fiscal_year_cut; period_start..period_end is what was aggregated, ZET-166). /gl/reports/* cuts by the line's stamped fiscal_year_id, so the two can differ on a line dated outside the year it is stamped to.

Inputs: company_id (required), month, with_prior, fiscal_year.

get_gl_account_ledgerAInspect

One account's ledger (Kontoauszug) — every booking that touched it, in date order, with Soll/Haben and the running balance after each line (CompanyMember).

No fiscal-year parameter: the chart is FY-owned, so account_id already fixes the year. Posted and reversed entries are included (a reversal is a second posted entry, so both legs must show or the balance is wrong); drafts are not. The running balance is carried across pages by the server — page_opening_balance enters this page's first row, while closing_balance/total_debit/total_credit describe the whole window. 404 when the account is not this company's; 422 when date_from is later than date_to.

Inputs: account_id (required), company_id (required), limit, offset, +3 more.

get_gl_journal_entryCInspect

One entry + lines, plus the subledger rows it produced/touched (Gap B detail surfacing): its gl_vat_posting rows, its gl_vat_zero_posting turnover-only declarations (zero-rated/exempt output — R2-13b: these have no VAT line to pair, so without them a correctly coded 0 % line is indistinguishable from an untagged one) and referenced gl_open_item rows. A declared base line also carries the resolved code on lines[].vat_code. Drafts carry empty lists. documents carries the accounting documents explicitly attached to the entry (POST …/documents) — the evidence for a hand-booked entry; a pipeline-created entry carries its document through source_ref_* instead and lists nothing here. Member read, like the rest of the detail.

Inputs: entry_id (required), company_id (required).

get_intakeBInspect

Get one intake row by id (scoped to its company: 404/403 split).

Inputs: intake_id (required).

get_itemDInspect

Item metadata (any source).

Inputs: item_id (required).

gl_trial_balanceAInspect

Per-account debit/credit columns for one fiscal year, with totals.

fiscal_year (year label) defaults to the latest year posted in; period_id narrows to one period of it. No all-years mode — account identity is (company, fiscal year, code), so aggregating double-counts silently (ZET-155). Unknown year/period → 404; period outside the year → 422.

Cut by the line's stamped fiscal_year_id, not its posting date; …/financial-statements cuts by posting date inside the same year's stored window, so the two differ only on a line dated outside the year it is stamped to. fiscal_year_cut names the cut (ZET-166).

Inputs: company_id (required), period_id, fiscal_year.

import_payroll_employeesAInspect

Import employees from the filled-in template (get_payroll_employee_import_template, .xlsx/.csv). All or nothing; existing employee_no rows are skipped. dry_run only reports. file_base64 is the file's raw bytes, base64.

Inputs: filename (required), company_id (required), file_base64 (required), dry_run.

ingest_expense_receiptAInspect

Upload ONE expense receipt to put on a claim: it is held from automatic booking; poll get_expense_receipt, then attach its item_id with attach_claim_receipt. file_base64 is the file's raw bytes, base64.

Inputs: filename (required), company_id (required), file_base64 (required).

list_ar_invoicesBInspect

List authored AR invoices, newest first.

Optional status / doc_type filter by lifecycle + document kind. Optional period (YYYY-MM) filters by the invoice's issue date (its month); a malformed value returns 422 {"msg": "period must be YYYY-MM"}.

Inputs: company_id (required), limit, offset, period, +2 more.

list_bank_accountsAInspect

The company's bank accounts — the bank_account_id every statement import, bank-entry list and reconciliation call needs (CompanyMember read).

Oldest first, no filter and no paging. Each row carries the iban, currency, label/bank_name and ledger_account_number — the chart code this account posts through; without one a bank movement cannot be coded, and it is set with PUT /bank-accounts/{account_id}.

auto_created marks an account inferred from an imported statement rather than declared by a human; it starts ownership_status unconfirmed with needs_ownership_review: true — confirm it before trusting its balances, since an unconfirmed IBAN may not be the company's at all. statement_count / entry_count are null here (filled by the single-account GET /bank-accounts/{account_id}), which is not the same as zero.

Inputs: company_id (required).

list_bank_entriesCInspect

Bank movements (statement lines), latest first.

Inputs: q, to, flag, from, +10 more.

list_companiesAInspect

List companies (jwt, scoped). Non-admins see only their member companies.

Inputs: no named parameters.

list_counterpartiesInspect

List a company's counterparties (filter by kind/q, paginated).

kind repeats to filter on a set (?kind=customer&kind=both) — a role-shaped picker asks for every kind that plays the role. A single ?kind=supplier keeps its original meaning.

Inputs: company_id (required), q, kind, limit, +1 more.

list_gl_accountsCInspect

List the postable chart (CompanyMember). fiscal_year filters to one year's chart (the chart is FY-scoped, so codes repeat across years).

Inputs: company_id (required), limit, offset, fiscal_year.

list_gl_journal_entriesAInspect

List journal entries.

period_ids narrows to specific fiscal periods, and is how a caller asks for one fiscal year: the year's period ids (ZET-285). Without it the route lists every fiscal year. total is the filtered total.

untagged_subledger_control=true narrows to the entries that posted to an AR/AP control account without touching the subledger, under allow_untagged_control (ZET-150) — the postings a subledger-vs-control divergence traces back to.

origin: one entry origin (ZEN-42). account_id: entries with a line on it; date_from/date_to: posting date; amount_min/amount_max: the entry total.

Inputs: company_id (required), q, sort, limit, +12 more.

list_gl_open_itemsAInspect

One page of the AR/AP subledger (member read).

direction filters server-side (ZCT-577); omit it for both. commercial_document_id narrows to one document's item (D09-G13); not with as_of.

as_of (ZCT-577) reconstructs each item's open amount from posted journal lines dated on or before that date, instead of reading today's cached amount. Items are considered regardless of their current status (one settled since that date was open on it), so status is refused alongside it rather than silently ignored. original_amount and status on each row remain the item's own, current facts.

Inputs: company_id (required), as_of, limit, offset, +4 more.

list_gl_periodsAInspect

The company's accounting periods — the months a journal entry may post into (CompanyMember read).

A period belongs to one fiscal year and carries period_no (1..12 within the year), date_from/date_to and a status: open accepts postings, soft_closed still accepts them, and closed/year_closed refuse them — a posting date inside a closed period fails until an accountant explicitly reopens the period (POST …/gl/periods/{period_id}/reopen, reason required, recorded in the close-run ledger — ZET-161). fiscal_year_id narrows to one year; omitted, every year's periods come back.

This is not the VAT filing calendar — those are the gl_vat_period rows of GET …/gl/vat/periods, which have their own quarterly/monthly cadence and their own filed/paid sealing. Use this list to find the period_id a manual journal entry needs, and to check why a posting date was refused.

Inputs: company_id (required), fiscal_year_id.

list_gl_vat_periodsCInspect

VAT return periods with status, filing and payment state, and the due windows.

Inputs: company_id (required).

list_itemsCInspect

List/filter items, scoped to the caller's member companies (A1).

Optional period (YYYY-MM) filters by the item's effective date (invoice date, falling back to the Europe/Zurich-local ingestion date); a malformed value returns 422 {"msg": "period must be YYYY-MM"}. exclude_triage_status drops items carrying that triage verdict (NULL-safe; for unrelated not a booked one, ZCT-954).

Optional q: a case-insensitive substring match over the filename and both counterparty names (linked, and extracted data.company).

duplicate filters on the row's is_duplicate flag (ZET-413); credit_note on its is_credit_note flag (ZET-429) — both server-side, so total stays exact. posted filters on the posting badge (ZCT-811): true = posted, false = held, reversed or not booked; a copy filed with the booking of the same invoice ("Already booked", posting.filed_with) is in neither (ZEN-1). overdue (D08-G14): due before today (Zurich), still owing, not a credit note. Owing is the open item's rest; a document with no open item is owing until a bank movement is linked to it (R2-2).

Inputs: q, paid, limit, order, +14 more.

onboarding_guideAInspect

How to onboard and create a NEW company: what to ask the user for, which documents to request, and the order to run the setup in.

Discovery does not depend on search: this tool is in the tier, so it is listed for every caller, and BASE_INSTRUCTIONS names it. find_operations does reach it ("new company setup" ranks it first), but a query made only of common words is still decided by whichever tool happens to contain them.

Read this before you start a company setup, and before you tell a user that something cannot be done here. It answers the questions the create's own schema cannot: which of fifteen sections actually matter, which documents produce them, and what it costs to skip one.

If your API key's purpose is onboarding, this is the only job it has.

Inputs: no named parameters.

post_gl_journal_entryAInspect

Post a draft entry into the books — accountant. One-way.

A posted entry can no longer be replaced or discarded (both refuse with 409); the only general correction is …/reverse, which leaves both the original and the reversal visible. The one exception is PUT …/guessed-account, which re-points a coding_guessed entry's expense account in place — and it works only on a posted entry. Check the draft before posting rather than after.

Inputs: entry_id (required), company_id (required), body.

process_statusBInspect

Is this company done, and what next (ZEN-2). Start and end here.

done: no held AI proposal, no unmatched or partly matched bank movement, Suspense explained, no unreadable, waiting, unreviewed or rejected-unbooked document (null when it cannot be checked). Lists every open item; work them through book_documents_act or reconcile_bank_act as each row's process says. Read-only.

Inputs: company_id (required), limit, offset.

reconcile_bank_actCInspect

One action on one open bank movement (ZEN-2), with its row's version: accept its held proposal, ignore it, skip / unskip. Ignore and skip need a reason; recorded with your user. Link and settle through the row's operations. Returns the new status.

On this MCP surface a null argument means "not provided": it is dropped before the request is sent, exactly as if the field were omitted.

Inputs: action (required), version (required), company_id (required), decision_id (required), +1 more.

request_api_keyAInspect

Ask the user to hand this session a Zeno API key. Use this first — every current Zeno user already has an account.

email is the address on their Zeno account. Ask them for it; you cannot guess it, and the request is aimed by it — Zeno will only show it to somebody signed in as the owner of that address. Pass client_name too: it is the only thing identifying you on the approval page, and without it the person is asked to trust "an unnamed client".

Returns a plain verification_uri. Tell the user to open it, sign in, and approve the request waiting there; we also email them a notice. There is no code, in either direction: nothing to read out, nothing to type, and nothing for you to put in a link.

Then call collect_api_key with the claim_token returned here, waiting poll_interval_seconds between calls, until its status stops being pending. The user chooses on the page what the key may reach — usually a single company — so expect the key to be scoped, and read a 403 elsewhere as that scope rather than as a failure.

The answer is the same whether or not that address has a Zeno account. If nothing ever arrives, the likeliest cause is a mistyped address — ask, do not assume.

Inputs: email (required), client_name.

reverse_gl_journal_entryAInspect

Storno a posted journal entry: post its mirror image (accountant role).

Nothing is deleted; the original stays, linked, and the reversal entry is returned. The only VAT-correct storno door — VAT postings, open items and what the document spawned are all unwound.

body.posting_date dates the reversal and decides its period; omitted, it reuses the original's. A closed-period entry needs one in an open period and a person: the reversal is booked there; the entry stays unchanged.

409 when: the entry is a reversal or already corrected; a payroll run holds it; the date falls in a filed VAT period; an open item still carries a live settlement; the target period is closed or sealed; or a closed-period entry cannot be corrected (the reason is named). A closed-period entry armed to reverse itself is left to the auto-reversal run (nightly, or POST …/gl/auto-reversals/run by a person): conflict.closedPeriodEntryAutoReverses.

Inputs: entry_id (required), company_id (required), body.

settle_entryAInspect

Post this reconciled bank entry into the GL (clean-bank settlement).

Matched → Dr Bank / Cr AR; unmatched → Dr Bank / Cr Suspense; a previously-suspensed entry now fully matched → Dr Suspense / Cr AR. Idempotent; skipped when the GL chart is not configured for native settlement.

Skonto (ZEN-526). cash_discounts names, per open item this movement pays, the cash discount the counterparty took, booked as POST …/gl/payments books cash_discount_amount. On an item a live payment of this movement already paid, it must be exactly what is left open (item currency); it follows that payment and is reversed with it. 422 when no Skonto account is configured, the movement pays nothing of the item (a link is not enough), cash + discount exceeds what is open, its VAT does not fit, or the settle books nothing for the item; 409 when a bill paid earlier is on an exported payment file. Nothing is booked on an error. Never proposed or applied without a person naming it.

Inputs: entry_id (required), body.

start_signupAInspect

Create a Zeno account for somebody who does not have one yet.

Use request_api_key first if they might already have an account — this tool cannot tell you, and deliberately never will.

We email email a verification link. The user opens it, sees that you asked (by the name in client_name, shown as an unverified claim), chooses their own password, and decides separately whether to connect you. You never see the link, and you must not ask for it: it is what proves they own the mailbox, and a link you could repeat is a link anyone could.

Then poll collect_api_key with the claim_token returned here. denied is terminal and means the person chose to create the account without connecting you, or refused outright — tell them plainly and stop; do not start another.

Inputs: email (required), client_name.

upload_accounting_documentAInspect

Upload a company's BALANCE SHEET, P&L or VAT return (PDF, PNG, JPEG, XLSX) to be read; queued, follow get_accounting_document. fiscal_year when the file does not say; force re-reads a file already read. file_base64 is the file's raw bytes, base64.

Inputs: filename (required), company_id (required), file_base64 (required), force, +1 more.

upload_accounting_importCInspect

Import a JOURNAL EXPORT (CSV/Excel) from another accounting system (source_system, e.g. bexio, abacus) and match it against the bank entries. file_base64 is the file's raw bytes, base64.

Inputs: filename (required), company_id (required), file_base64 (required), source_system (required), +1 more.

upload_bank_statementAInspect

Import a BANK STATEMENT. CAMT.053 XML books at once; PDF, CSV, .xlsx queue (list_bank_statement_imports); .zip splits; legacy .xls, UTF-16 CSV refused. CSV/.xlsx imports only if opening + lines = closing, else nothing; with no printed opening/closing balance it fails until the person's balances per balances_needed (and the account if no IBAN) come via assign_bank_statement_import_accounts. file_base64: raw bytes, base64.

Inputs: filename (required), company_id (required), file_base64 (required).

upload_documentAInspect

Upload an INVOICE or RECEIPT (PDF, image, or .zip of them) for analysis. file_base64 is the file's raw bytes, base64-encoded. direction is payable (incoming supplier invoice) or receivable (outgoing). Creates Item(s) and queues extraction.

This door is invoices-only: it never routes a file onward by type, so a bank statement, a journal export or a balance sheet sent here is analysed and then just sits as a document. For anything that is not an invoice — or when you are not sure what the file is — use upload_intake.

Inputs: filename (required), company_id (required), file_base64 (required), direction.

upload_intakeAInspect

Upload ANY file; the system decides what it is (the unified intake queue, the web app's Documents > Upload). file_base64: raw bytes, base64.

Prefer this unless plainly an invoice; always for bank statements (CAMT.053 XML, PDF, CSV or .xlsx; not legacy .xls), matched to the registered bank account by IBAN; journal/accounting exports; balance sheets, P&L and VAT filings. A mixed .zip is routed per file.

Returns 202 and the queue row; poll get_intake for the outcome and targets. An unroutable file fails with its reason, never dropped.

Inputs: filename (required), company_id (required), file_base64 (required).

whoamiAInspect

Which user this request acts as, and which company's books it is bound to (jwt or API key).

Zeno serves every tenant from one host, and an API key is opaque — nothing else tells a connected agent whose books it is about to write. Call this FIRST when working over MCP: company_scoped: true means this connection's data access is confined to company_id — company_name names it (null here means the bound company no longer exists), no other tenant is reachable, and the admin endpoints are refused however privileged the owner is. is_admin is that owner's bit: worth nothing outside this company, still full authority inside it, so a scoped key with is_admin: true may write these books even when company_role is null. company_scoped: false means the credentials carry the owner's full principal and memberships lists the companies it can act in. Read-only and cheap — at most one lookup. ZET-171, ZET-176.

credential_purpose says which kind of credential this is, and is what the withholding rule keys on (SP-08): anything that is neither full nor session is confined, and gets memberships withheld — null, not empty.

Working over MCP, what you book or accept is recorded as MCP — not as this user acting in person — and the app displays it that way.

capabilities says what this caller may do, each verdict computed from the predicate the gate itself evaluates (SP-12) — so an agent learns what it cannot do before it collides rather than after. A credential confined to a company gets the entries whose verdict is a fact about the credential; the one that would read the owner's estate (create_company) is omitted, because its verdict would disclose a sibling tenant. A credential confined to no company — an onboarding key — has no sibling to disclose and does get it, which is the one operation such a key exists to call. pending_admin_actions is present and empty until PRE-03/PRE-04 fill it.

Inputs: no named parameters.

zeno_infoAInspect

What this server is, which MCP revision it speaks, and how to get a credential.

Needs no credential. Call it first if a tool has just refused you: the authentication block names the tools that can get this session connected.

Inputs: no named parameters.

zeno_overviewAInspect

What Zeno does, in one page — the platform's capabilities and its limits.

Needs no credential. Read this before telling a user that Zeno cannot do something; it covers VAT, payroll, reconciliation and the AI accountant.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      B
      maintenance
      Free, open-source (MIT), local-first Swiss accounting MCP server: an AI agent posts double-entry journal entries, categorises and chases invoices, and prepares the MWST-Abrechnung (the Swiss VAT return), with a minimalist Studio for human oversight. Posted entries are append-only and immutable, corrections are reversing entries, and every query is tenant-scoped.
      500
      477 npm
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables Czech freelancers to issue legally complete invoices and credit notes, record expenses and payments, generate VAT and income-tax filings, and manage bookkeeping from an AI chat or a local dashboard.
      25
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables Dutch sole proprietors with few invoices to keep their books through an existing AI assistant, handling invoices, receipts, btw returns, KOR tracking, and year reports using deterministic Dutch tax rules.
      24
      AGPL 3.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources