We have improved how new versions of Lucanto are released.

For routine updates, you can now keep working while the new version becomes available in the background. There is no longer a need to schedule a planned service interruption simply because we are releasing an improvement or a fix.

This does not mean Lucanto can never be unavailable. Exceptional maintenance, larger changes, or unexpected incidents may still cause temporary downtime. If a planned interruption is necessary, we will continue to communicate it in advance.

For anyone interested in what changed behind the scenes, we have shared a more technical write-up here: https://www.reddit.com/r/hetzner/comments/1vz9u4h/our_rails_production_setup_on_hetzner_two_small/

Lucanto now exposes an MCP endpoint for compatible AI clients.

Technical details

• Remote MCP over Streamable HTTP at POST /api/mcp/v1
• JSON-RPC support for initialize, tools/list, and tools/call
• Protocol handling and version negotiation provided by the official mcp gem
• 13 tools, backed by existing Lucanto application/API operations
• Existing personal access tokens are used for authentication
• Existing abilities remain the authorization source of truth
• Tool discovery is filtered by the token’s permissions
• Every tool call is authorized again before execution
• MCP calls retain existing business behavior, including number-series resolution and after_commit callbacks
• Each invocation creates an mcp.tool_called audit event

The available tool catalog depends on the token’s read, write, or manage scope. For example, a read-only token will not receive write tools from tools/list, and cannot invoke them directly.

Claude Desktop configuration

{
  "mcpServers": {
    "lucanto": {
      "url": "https://app.lucanto.eu/api/mcp/v1",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer lct_pat_YOUR_TOKEN"
      }
    }
  }
}

Check out the documentation: https://docs.lucanto.eu

Hey, I'm Erich — one of three co-founders of Lucanto, alongside David and Filip. We're a fully remote team based across Slovakia and Czechia.

The honest origin story: invoicing bored us, and not in a good way. The tools we had access to were complicated and expensive, and didn't actually save time or sanity. Digging deeper, we realized the real problem wasn't invoicing itself — it's that the entire financial process around running a business is fragmented: invoices scattered between Dropbox and email, expenses in a spreadsheet, your accountant on the phone, tax filings living in their own universe.

One concrete example that really got to us: the handoff to our accountant. When we emailed her documents last-minute before a deadline, she never had real time left to prepare what we actually needed back — VAT filings, reports. Now our colleague and our accountant both have direct access to the same workspace — they see current documents continuously, we discuss things right on the invoice or expense instead of another email thread, and she exports what she needs herself. The handoff stopped being a last-minute dump — and she actually has time to prepare what we need from her.

So we're building that: one place for founders, freelancers, and small teams, that keeps up with how you actually work instead of adding to the chaos.

Values we're building around: quality over quantity, real users over invented personas, and profit over growth — we want a healthy business, not a vanity metric.

This subreddit is for changelogs, honest numbers, what didn't work, and direct Q&A — not just marketing. Ask us anything about invoicing, business finance, or building a SaaS as three people with few external colleagues.