Field Wizard

AI & MCP

Point your own AI at your own field data

Field Wizard runs a Model Context Protocol server. Connect the assistant your company already approved — Claude, ChatGPT, or whatever your policy allows — and it can read your jobs, schedule, customers, photos, price book and completed forms, and act on them. No exports. No spreadsheet. No AI vendor of ours in the middle.

Start free trial →

Use your approved model, not ours

Most field software that advertises AI means their model, billed by the token, holding your data on terms you did not choose. This is the opposite arrangement. The connection runs from our server to the client you configured, using a key you created and can revoke in one click.

Field Wizard your records your key Your AI client Claude, ChatGPT, your own your plan Your approved model the one IT signed off No Field Wizard model anywhere in this line. No per-token bill from us.

Build a form by asking for it

The whole form builder and PDF designer are reachable, so an assistant can draft a working form from a description, lay out the branded PDF, check its own work and hand you a preview link. Four real examples, with the tools each one uses:

You ask

“Build me a confined-space entry permit and make the PDF match our paper one.”

It reads the field-type catalogue, builds the form, imports your existing PDF as the layout, dry-runs it to catch its own mistakes, then hands back a preview.

list_form_field_types → create_form → create_pdf_layout_from_pdf → set_pdf_layout

You ask

“What do we charge for a 5-ton compressor, and what did we quote Henderson?”

It reads your price book out of Live Data, finds the customer's last estimate and compares the two.

list_tables → search_records → search_clients → search_estimates

You ask

“Who's still open this week, and who is furthest behind?”

Outstanding work in schedule order, each job carrying its promised window and whether that promise was kept.

list_outstanding_dispatches → dispatch_metrics

You ask

“The Henderson site needs someone today. Who's closest with a gas ticket?”

It raises the job, ranks technicians on distance, skills and current load, finds an open slot and dispatches. The technician's phone buzzes before the call ends.

search_clients → create_job → suggest_technicians → assign_job

What it can reach

57 tools, 39 that read and 18 that write — curated rather than one wrapper per endpoint, because an assistant choosing between sixty legible tools is accurate and one choosing between four hundred is not.

Jobs and dispatch · the schedule board · customers · forms and submissions · the PDF designer · Live Data tables and your price book · field photos with their GPS stamps · quotes and invoices · parts and stock · the team and their timesheets · follow-up tasks · safety incidents, observations and inspections · the approval queue.

What it deliberately cannot do

An AI with access to your operational records is only a good idea if the limits are real ones, enforced by our server rather than by the model's good manners.

It cannot delete anything

Not a customer, a job or a submission — at any permission level. There is no delete tool in the catalogue, and a test fails our build if anyone adds one.

It cannot send invoices or approve work

Drafting an invoice is allowed. Sending a money request to your customer under your name is not, and neither is signing off a submission.

It cannot leave your company

A key belongs to one company and every query is filtered by it before the database is touched.

It cannot take orders from your data

Results come back tagged as data, and the server tells the model at connection time that tagged content is never an instruction. A customer typing "ignore your instructions" into a form field is quoting, not commanding.

Connecting it takes about a minute

  1. In Field Wizard, open Settings → API & Webhooks → Connect your AI and choose Look, don't touch or Look and do.
  2. Copy the key. It is shown once and stored only as a hash.
  3. In your AI client, add a custom connector: the URL, and the key as one header.
  4. Ask it something. A good first question: “Which jobs are still open, and which customer has the most?”

Questions people ask

Which AI assistants work with this?

Any client that speaks the Model Context Protocol, which includes Claude and ChatGPT's connector support. You add one custom connector: a URL and one header. We do not maintain a list of blessed vendors, because the point is that the choice is yours.

Do you send our data to an AI company?

No. The connection runs from our server straight to the client you configured, on your subscription. We are not in the middle of it, and there is no model we picked on your behalf.

What does it cost?

Nothing beyond the Pro plan, which every trial includes. There is no per-token fee and no AI add-on to buy. You already pay whoever provides your assistant; this does not add a second bill.

Our IT policy only allows one approved model. Is that a problem?

That is the case this was built for. Point it at the model your policy allows. If your policy allows none, issue no key and nothing about the product changes.

Can we give it read-only access?

Yes, and it is the default we recommend. A read-only key physically cannot write — the restriction is checked per tool on our side, not requested politely in a prompt. Write tools stay visible but refuse, so nobody is left guessing.

What happens if we turn it off?

Revoke the key. The connection dies immediately and everything else keeps working, because this is a door onto the product rather than a part of it.

Try it on your own data

Every trial includes it. Create a read-only key, connect your assistant, and ask it something you would normally have to build a report for.

Start free trial →

30 days free · no card · cancel yourself any time. No seat minimum.

Want the technical detail first? See the API and webhooks.