Employees in a professional-services firm need one place to submit expenses, group them into weekly reports, and track payment status through finance, and the prompt shows how to build an expense management app with ToolJet MCP as a structured ToolJet application, with data, queries, and interface working together. You get the finished internal app for expense submission, manager review, and reimbursement tracking, instead of a screen mockup or a loose code drop. The same structure keeps operational state visible as claims move from draft to payout, and the prompt in this article is what you can reuse for your own team. That matters when policy checks, approvals, and payment status have to stay visible as work moves.

ExpenseSheet

The first page opens with a title and purpose line, then keeps the action surface compact with summary tiles, spending visuals, and a needs-attention panel. A segmented control switches between the claim list and the report list, and each row opens in a modal so the canvas stays focused on one task. The second page follows the same pattern for decision work. You review submitted reports in an inbox, inspect line items inside a modal, and watch reimbursement status in a separate queue while the policy reference stays nearby. The review modal keeps the approval history visible during the decision, so the page reads like an operations console rather than a pile of tables.

• Compact employee workspace with action-oriented summary tiles, spending visuals, and a needs-attention panel
• Segmented claim and report view so only one table is on screen at a time
• Modal-based expense detail and line-item review without crowding the canvas
• Manager and finance review flow with approval history visible in context
• Policy reference table and reimbursement queue kept close to the decision flow

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 been used from the start. You can feed this version straight into the same workflow and reproduce the application in one shot.

ToolJet MCP works through the whole application, so the data model, pages, components, queries, and the wiring between them land as one structured ToolJet application. Enterprise app building does not stop at the interface, because data connectivity, workflows, permissions, deployment, and ongoing change are part of the runtime where supported, not a separate codebase you have to operate yourself. That keeps the path open from AI generation to visual editing, and then into code when a field, rule, or workflow needs finer control.

The app ended up with seven tables. exp_employees stores the people and their approvers, exp_policies holds reimbursement rules, exp_expenses records each claim, exp_weekly_reports groups claims by week, exp_report_expenses links reports to lines, exp_approvals keeps the decision trail, and exp_reimbursements tracks payment progress. That split keeps report membership separate from the expense row, which is what makes partial approval and later payment updates stay clear.

This build shows an employee creating an expense, bundling it into a weekly report, a manager reviewing the lines, and finance carrying the reimbursement through to payment status. The output is a real ToolJet application on a mature runtime, so you keep editing the same pages and queries after generation instead of taking ownership of generated code. That matters because the data model, workflow, and review trail stay tied together, and the same app can remain mostly visual while still dropping into code when a case needs it.