Cogny CLI · Finance

    Fortnox queried from Bash.

    Read invoices, supplier invoices, vouchers, accounts, customers and financial years from your Fortnox books — from the shell over the Fortnox MCP. Pull the ledger as JSON for revenue, AR aging, and reconciliation, no login.

    # 1. sign up (free for 15 calls) — uses your git email
$ npx @cogny/cli init --agent claude-code

# 2. see every Fortnox tool
$ cogny tools list

# 3. call any tool from Bash — no MCP wiring
$ cogny tools call mcp__Fortnox__list_invoices --input '{…}'
    ❯ start Cogny Solo — $9/mo@cogny/cli on npm →
    ❯

    cogny --who

    TWO PATHS
    You're a human

    Checking AR aging or reconciling spend against the books means clicking through Fortnox screens and exporting. The CLI returns invoices, payments, and vouchers as JSON you can pipe into a reporting step. Connect Fortnox once in Cogny Solo and let your coding agent — or scheduled reports — do the querying for you.

    ❯ start Solo
    You're an agent

    Self-onboard with one command. The CLI issues a key, wires nothing, and exposes every Fortnox tool over JSON-RPC. First 15 calls are free.

    $ npx @cogny/cli init --agent claude-code
    ❯

    cogny tools call

    3 EXAMPLES

    Real tool names from the Fortnox MCP. Send --input JSON, get JSON back.

    mcp__Fortnox__list_invoicesList customer invoices, filtered (e.g. unpaid).
    $ cogny tools call mcp__Fortnox__list_invoices \
  --input '{"filter":"unpaid","limit":2,"sortby":"duedate","sortorder":"ascending"}'
    example response
    {
  "Invoices": [
    {
      "DocumentNumber": "1142",
      "CustomerName": "Acme AB",
      "Total": 18750,
      "Balance": 18750,
      "DueDate": "2026-05-30",
      "Currency": "SEK"
    },
    {
      "DocumentNumber": "1147",
      "CustomerName": "Beta HB",
      "Total": 9200,
      "Balance": 9200,
      "DueDate": "2026-06-10",
      "Currency": "SEK"
    }
  ]
}
    mcp__Fortnox__get_invoiceRead a single invoice with line rows.
    $ cogny tools call mcp__Fortnox__get_invoice \
  --input '{"document_number":"1142"}'
    example response
    {
  "DocumentNumber": "1142",
  "CustomerName": "Acme AB",
  "Total": 18750,
  "Balance": 18750,
  "Booked": true,
  "InvoiceRows": [
    {
      "Description": "Consulting May",
      "Price": 1500,
      "DeliveredQuantity": "12.5"
    }
  ]
}
    mcp__Fortnox__list_vouchersList accounting vouchers for a financial year.
    $ cogny tools call mcp__Fortnox__list_vouchers \
  --input '{"financialyear":5,"limit":2}'
    example response
    {
  "Vouchers": [
    {
      "VoucherSeries": "A",
      "VoucherNumber": 412,
      "TransactionDate": "2026-06-14",
      "Description": "Customer payment 1138"
    },
    {
      "VoucherSeries": "A",
      "VoucherNumber": 411,
      "TransactionDate": "2026-06-13",
      "Description": "Supplier invoice 9921"
    }
  ]
}
    ❯

    cogny tools list

    MORE

    A sample of the rest of the Fortnox surface. Run cogny tools list --json for every tool and its input schema.

    mcp__Fortnox__get_company_informationmcp__Fortnox__list_customersmcp__Fortnox__get_customermcp__Fortnox__list_supplier_invoicesmcp__Fortnox__list_invoice_paymentsmcp__Fortnox__get_vouchermcp__Fortnox__list_accountsmcp__Fortnox__list_financial_yearsmcp__Fortnox__list_orders
    ❯

    cogny --faq

    Is this an official Fortnox CLI?

    No — it is the Cogny CLI calling the Fortnox MCP over the cogny-mcp-proxy. You connect Fortnox once in Cogny, then read the ledger from Bash. Fortnox AB is not affiliated.

    Can it modify the books?

    No — this MCP is read-only by design. Fortnox OAuth scopes are coarse-grained and cannot enforce read-only at the token level, so write tools (create/update/bookkeep invoices and vouchers) are intentionally not registered. You can only query.

    What can I build on it?

    Revenue-vs-baseline reports, AR aging from `list_invoices` (unpaid filter), and reconciling ad/supplier spend against `list_supplier_invoices` and `list_vouchers` — all as scheduled JSON pulls.

    ❯

    related CLIs

    /cli/shopify→/cli/woocommerce→/cli/upsales→/cli/ga4→

    Building an agent? The full tool map for all servers is one fetch: /cli/llms.txt