Fieldproxy guide

Can AI customise my field service software?

Updated September 27, 2026

Short answer

With Fieldproxy, yes: you ask Claude, ChatGPT or Microsoft Copilot for a change, such as a new field, a screen or an automation, and its MCP server builds it as a draft in a sandbox copy of your workspace. It goes live only when an administrator approves, and it can be rolled back. The other field service AI connectors we checked (Jobber, ServiceM8 and community servers for ServiceTitan and others) read and edit records but cannot change the software itself.

What you can ask for

These are changes that normally mean a support ticket, a consultant or a months-long roadmap wait:

  • "Add a warranty expiry date to every job." A new column, the form field and the list column.
  • "Build a subcontractor compliance screen that flags missing insurance or licence." A new table and screen.
  • "Email the service manager 30 days before a warranty runs out." An automation, saved switched off.
  • "Add a tool that lists a customer's overdue invoices." A saved SQL tool every AI connection can call.
  • "Create a text agent that answers where-is-my-technician questions." A text agent, simulated before it is enabled.

How the change is kept safe

Customising live business software from a chat window only works with guardrails. Fieldproxy's build tools save every app change as a draft, and saving or publishing is blocked if the linter, a SQL check against the database or a navigation check finds a new error.

Build work happens in a sandbox: a copy of the workspace, made at most once every 24 hours and kept up to 90 days. You plan and confirm a promotion to live. Tables and columns are only ever added, never dropped, and public apps are never changed by the AI.

Only administrators can build, and only when the workspace has Allow build switched on.

Which field service tools let AI change the software

As of September 27, 2026, based on each vendor's published MCP documentation:

SoftwareAI connectorCan change the software
FieldproxyOfficial MCP serverYes: fields, screens, tables, automations, agents
JobberOfficial connectorNo: reads records; creates requests, clients, properties
ServiceM8Official MCP serverNo: reads records; creates and schedules jobs, sends messages
ServiceTitan, Housecall Pro, Simpro, Workiz, JobNimbusCommunity or third-party onlyNo

Fieldproxy facts on this page come from the Fieldproxy MCP reference. Competitor details are from each vendor's own documentation as of September 27, 2026; see the comparison table and sources.

Illustration of Fieldproxy's MCP tools inside Claude, ChatGPT and Copilot. Names and data are examples.

FAQ

Questions

Do I need a developer to customise Fieldproxy?
No. An administrator describes the change in plain English to Claude, ChatGPT or Copilot, reviews the draft in the sandbox and approves it.
Can a technician change the app by accident?
No. Building needs the build scope, an administrator role and Allow build switched on for the workspace. Everyone else can at most propose data changes that a person confirms.
What happens if an AI-built change is wrong?
It is caught by the checks before saving, reviewed in the sandbox before going live, and can be rolled back after.

See it on your operation

We connect Claude, ChatGPT or Copilot to a Fieldproxy workspace built on your data and run your real questions.