You build an asset handover app with ToolJet MCP for a commercial construction equipment store that still tracks tools on paper, so staff can scan a QR code and see who has each item and in what condition. Asset Handover Station turns that workflow into a tablet app that records issue, return, and transfer events from one screen. An agent generated the app, and the result is a structured ToolJet application, data, queries, and interface together, that the team keeps running instead of a screen or a code drop.

Equipment List — KPI tiles, category breakdown, recent activity, and a searchable, filterable table with an overdue view

Item Detail — full movement history with condition photos, and an Asset-Manager-only correction flow

Scan & Record — QR scan with a manual-code fallback, big Issue/Return/Transfer buttons

The first page centers on a large scanner, a manual code field, and the three movement actions. A matched item opens with the asset name, category, current holder, and condition already visible, while an unmatched scan shifts into a compact register form that creates the asset and continues straight into the movement step. The same screen keeps the recipient, condition now field, expected-return date, and photo capture controls close to the confirm action, so the user can finish the handover without moving across the app. The second page turns the log into an operating view with filters, counts, category mix, recent activity, and a row list that opens the full asset history.

• Big QR scanner with a manual-code fallback
• Issue, return, and transfer actions from one tablet screen
• Return photos upload to S3 and stay attached to the movement
• Equipment list with filters, overdue sorting, and recent activity
• Hidden item detail view with full movement history

Want to build it yourself? Start with the ToolJet MCP repository for setup instructions, supported agents, and everything you need to follow along.

The real build took several passes, and the requirements are consolidated here into one prompt that could have driven the same app from the start. You can use it as a single-shot spec and reproduce the layout, data model, and handover rules without reconstructing the iterations.

ToolJet MCP takes the requirements and works through the item model, the scan page, the list page, the hidden detail view, the queries, and the wiring between them, so the output lands as one structured ToolJet application. Enterprise app building does not end at the interface, because data connections, permissions, deployment, and ongoing change stay part of the job, and the generated app sits on a runtime that carries those where supported instead of leaving you with a codebase to operate yourself. After generation, the path stays open for visual edits and code where a specific rule or layout needs it, which is what keeps the app editable when the handover process changes.

A QR code scan looked wrong on screen because the decoded value carried trailing whitespace, so the lookup missed the matching item. Trimming the scan value fixed the match, and the same asset now opens on the first scan with the right movement flow.

The app ended up with two tables. items stores every tracked asset, and movements keeps the append-only log of issue, return, and transfer events, including condition changes, notes, photo URLs, and correction history. The current holder and condition come from the latest movement instead of a mutable status field, so the scan view and the list view stay in sync.

Commercial construction and equipment rental — any company that hands physical power tools, survey equipment, or site laptops between crews and needs an auditable record of who has what and in what condition, without relying on a paper sign-out sheet.

Operators can scan items, record issues/returns/transfers, and view full item history read-only. Asset Managers get everything Operators have, plus the ability to correct a mistaken movement record after the fact — enforced server-side on the correction query itself, not just hidden in the UI.

An asset handover app handles asset codes, current holders, and return dates. ToolJet covers that governance at the platform layer, so you configure it once instead of rebuilding it in every app.

• SSO and SCIM: sign in with SAML, OIDC or LDAP, and provision users automatically
• Role-based access control: scope permissions to the app, the data source, and each query
• Audit logs: track every login, edit, and approval decision for compliance review
• Air-gapped deployment: self-host on Docker or Kubernetes so your data stays in your network
• Multiplayer editing: several builders work on the same app, with versioning and Git sync
• ToolJet AI inside your own deployment: run the AI features in your tenancy rather than a shared service

This build shows that a paper handover ledger can become a working tablet app with scan, record, list, and detail flows tied to a live item log. The useful part is not just the interface, it is the structured application behind it, because the app keeps its data model, queries, and screens together after generation. That matters when the asset rules change, since you can keep editing visually, drop into code for a narrow fix, and rely on the runtime for data and workflow behavior where supported, instead of treating the generated app as a disposable artifact.

You can easily build a 4-page app with ToolJet MCP for as little as $0.17 with a lean model (Luna medium), or pay more for the latest flagship reasoning (Sol) if that’s what you’re after. The cost is your call, not a floor we set for you.

Three to four builds per model across four-page apps. 1 credit = 1 cent. Credits and time are estimates only and will vary with the complexity of what you ask for. This measures cost and speed only, not how complete or polished the result is.

Even averaging across model tiers, ToolJet MCP can turn $10 into a dozen or more working 4-page apps.