Introduction
You build a device register with ToolJet MCP when a multi-academy trust needs one place to issue, return, move, and write off laptops and tablets across 11 schools instead of chasing per-school spreadsheets. The app in this article turns that brief into a structured ToolJet application, with data, queries, and interface kept together so the team keeps running the register rather than juggling a screen and a separate code export. The result gives device coordinators and finance staff one live place to manage stock, history, and the handovers that happen every term.
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.
Scan & Record: look up a device by asset tag and issue, return, move or write it off
Register: every device across all 11 schools, searchable by school and status
Summary: per-school breakdown chart and the damage-charge approval queue
What We're Building
The home page centres on a scan panel and a device detail card, so the user starts from one asset tag and moves straight into action. A camera scan or manual entry fills the card with school, holder, status, and condition, while a recent-activity feed keeps the last scans and actions visible during the session. Bulk issue mode changes the flow for a class rollout: pick the class, scan devices one by one against a running count, and use Undo to roll back the last scan when the wrong device is entered. Opening a device in the Register page brings up the full movement history in a modal, and the Summary page pulls the counts and damage-charge queue into one view for finance.
- Camera scan with manual asset-tag fallback
- Centered device detail panel with school, holder, status, and condition
- Recent activity feed for the latest scans and actions
- Bulk issue mode with class selection, running count, and undo
- Damage found on return becomes a finance review queue, not an automatic charge
Build a Device Register with ToolJet MCP for Trust Teams
Want to build it yourself? Start with the ToolJet MCP repository for setup instructions, supported agents, and everything you need to follow along.
The Consolidated Build Prompt
The build took several passes, and the requirements now live in one prompt you could have used from the start. Read it as a single-shot specification, then use it to recreate the same app without reconstructing the earlier iterations.
Build a 3-page device register app in ToolJet for Northline Learning Trust, a multi-academy trust with 11 schools, to replace per-school spreadsheets for laptops and tablets. No permissions system for now, every signed-in user can act as any staff member.
Page 1, Scan & Record, is the home page. Staff scan a device's asset tag with the camera or type it manually, then see the device's school, current holder, status, and condition in a centered panel that starts greyed out before a scan. From there they can issue to a pupil or staff member, return, move, or write off a device, with a recent-activity feed and a bulk issue mode for the September rollout, including class selection, repeated scanning, and undo. Issuing to a pupil captures the accepted-by name. Returning a device can record damage from a fixed damage-type list with an optional photo, and any damage creates a proposed charge for later finance approval.
Page 2, Register, is a searchable table of every device with school and status filters, plus a modal that shows current details and the full movement history. Page 3, Summary, shows owned, on loan, overdue, and written off this year as a KPI strip, a grouped chart across all 11 schools, and a queue of proposed damage charges with Approve and Reject actions.
Use schools, staff, classes, pupils, a fixed damage-type list, devices, device movements, loan agreements, and damage charges. Device movements are the audit trail, loan agreements capture the accepted-by record, and damage charges stay proposed until finance acts. Design it as enterprise-grade but warm and approachable, with warm oranges, soft shadows, rounded corners, muted colours, a trust-naming header band, the signed-in-as identity and logout control inside it, and one consistent panel type size.
How ToolJet MCP Builds the App
ToolJet MCP works through the whole application, not just the screen, so the data model, pages, components, queries, and the wiring between them land as one structured ToolJet application. Enterprise app building does not end at the interface, because data connectivity, workflows, permissions, deployment, and ongoing change still sit behind the register, and the generated app lives on a runtime that carries those where supported instead of handing you a codebase to operate alone. The path stays open after generation, with visual editing for normal changes and code where a device rule or data transform needs it.
Data Created
The app ended up with 9 tables, split across the trust roster, the device ledger, and the finance trail. schools, staff, classes, and pupils anchor who can hold a device, damage_types and devices define what the register knows, and device_movements, loan_agreements, and damage_charges keep the history and review queue tied to each asset.
| Page | Components | What they cover |
|---|---|---|
| Scan & Record | 57 | Scan or type an asset tag, see the device panel, and issue, return, move or write off a device, plus bulk issue mode |
| Register | 13 | Searchable register of every device with school/status filters and a full history modal |
| Summary | 10 | Per-school breakdown chart, KPI strip, and the damage-charge approval queue |
What Got Generated
| Metric | Result |
|---|---|
| Pages | 3 |
| ToolJet DB tables | 9 |
| Queries | 32 |
| Components | 80 |
| Code files to maintain | 0 |
| Repair cycles | 1 |
| Final validation | 0 error |
Industries That Run This
Multi-academy trusts and school IT teams are the direct fit here. The same pattern, a scannable asset register with an issue, return, move or write-off lifecycle, loan agreements, and damage charges routed for approval rather than auto-applied, suits any organisation that hands out shared hardware to people it doesn't directly employ or fully control: universities issuing laptops to students, healthcare trusts tracking mobile devices and equipment across wards, and corporate IT teams managing a loaned-device fleet across offices.
Who Gets Access To The Built App
Permissions were explicitly left out of this build. Anyone signed in can pick any staff identity from the header and act as them: issue, return, move or write off any device at any school, and approve or reject any damage charge. It's built as a shared operational tool for school IT staff, not a role-restricted system; adding real per-school or per-role access control would be a natural next phase.
Enterprise Features for Your Device Register App
A device register holds asset tags, pupil names, and loan agreements. 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
ToolJet Workflows adds the notification layer. One workflow fires when a damage charge is approved, posts the finance decision in Slack, emails the school through Gmail, and writes the result back to damage_charges.
Final Takeaways
This build shows a trust-wide device register can move from one prompt to a working app that handles scan, register, summary, and finance review flows around the same shared data. The result matters because the agent produces a structured application on ToolJet's runtime, so the team keeps editing the app instead of inheriting a code export and its upkeep. That model leaves room for visual changes, targeted code when a rule is special, and the data, workflow, and governance layer that keeps device history, damage review, and future changes in one place.
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.
Try ToolJet MCP
Build your own device register for a multi-academy trust, then request a ToolJet demo.
FAQs
What does ToolJet MCP do for a device register?
ToolJet MCP turns a written brief into a working ToolJet app by shaping the register's pages, data, and interactions together. For this build, that means a scanner-led device register rather than a static mockup or a pile of scripts.
What does the Device Register app actually do?
The app tracks laptops and tablets across 11 schools, then lets staff issue, return, move, and write off each device. It also keeps movement history, loan agreements, and damage charges attached to the same record.
How do you reproduce the build from the prompt in this article?
Use the prompt in this article as the full specification and run it as one build request. The same pages, tables, and rules can be recreated without turning the brief back into a manual checklist.
Do you need to write code for the scanner and history views?
Not for the core flow. The app shows the scan panel, device details, recent activity, register filters, and history modal as part of the generated application, and you only drop into code when a special rule needs it.
What happens after the agent finishes, is this just a UI generator?
No, the output is a structured ToolJet application that keeps the data, queries, and interface together on the runtime. You keep editing the app visually, add code where needed, and let the same project carry the device rules forward.
Can the app use your own device data?
Yes, the same register shape can point at your own trust data instead of the seeded demo content. The device list, movement log, loan records, and damage queue are all built around that shared model.
Can several people keep building on the same Device Register app?
Yes, the same ToolJet app stays as one shared project, so different builders can keep extending the register without splitting the logic across separate copies. That helps when the trust updates device rules or adds a new school process.
Top comments (1)
Great breakdown of building enterprise apps with ToolJet MCP. What stands out is that the workflow is moving beyond just generating UI components it is connecting data models, queries, business logic, and application structure together.
The device register example is a good representation of how internal tools are often built in real organizations: asset tracking, approvals, audit history, and operational workflows are usually more valuable than a simple CRUD interface.
I think the interesting direction is how MCP-based development can reduce the gap between business requirements and working applications. Instead of spending weeks translating requirements into tickets, teams can iterate faster while still keeping control over architecture, security, and governance.