Plumbing · Fieldproxy MCP

Run your plumbing operation from ChatGPT, Claude or Teams

Your plumbing workflow is not anyone else's. Ask the assistant to add the field, screen or alert you need and it builds it, then runs the day on your live jobs, with your OK before anything changes.

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

Short answer

How can a plumbing company use ChatGPT, Claude or Copilot?

Connected through MCP, ChatGPT and Claude can answer from your live plumbing jobs and do the work: re-route emergency call-outs, follow up on open quotes and find completed work that was never invoiced. Fieldproxy's MCP server asks you to confirm every change and can undo it.

Last verified September 27, 2026

Real asks

What plumbing teams ask it

"Which quotes over $3,000 went quiet more than 10 days ago?"

The list with drafted follow-up emails, sent only when you confirm.

"Fit this burst-pipe call into today's board without breaking any SLA."

The nearest qualified tech, the jobs that shift, and the customers to notify.

"Show me the photos from the Oak Street job before I sign it off."

The job's photos in the chat, compared before and after.

The part nobody else does

Your AI can change the software, not just the data

Every other field service connector we checked (September 27, 2026) reads records and, at most, edits a few of them. Fieldproxy's MCP server can also build: new fields, screens, tables, automations and agents, made in a sandbox copy of your workspace and live only when you approve.

Add a field

"Add a warranty expiry date to every job." The column, the form field and the list column, in one ask.

Build a screen

"Build a subcontractor compliance screen that flags missing insurance." A new screen on your real data.

Wire an automation

"Email the service manager 30 days before a warranty runs out." Saved switched off until you turn it on.

Create an agent

Voice and text agents: validate, simulate against test conversations, then enable.

Add your own tools

Saved SQL tools such as "a customer's overdue invoices", which every AI connection in the workspace can then call by name.

Roll back anything

Every build is checked against your database before it saves, promoted from the sandbox when you approve, and can be rolled back.

What your AI can do

145 tools, across the whole field operation

Not just lookups. The assistant can plan the schedule, send the follow-up and build the screen, and every change waits for a person to confirm.

Read

Customers, jobs, technicians, invoices, quotes and contracts. Accounts-receivable ageing, technician performance, funnels, and read-only SQL against your own schema.

Dispatch and maps

Spread jobs across technicians, plan daily routes and apply the schedule. Drive times, the nearest technician, live locations and job sign-off links.

Comms

Search the inbox and read threads. Draft emails and SMS from templates, then send after you confirm. Comments, notifications, email follow-ups and phone calls.

Sales documents

Preview and issue proposals, generate estimates and PDF documents.

Files and photos

Read a record's PDFs, Word, Excel and email files, and look at the photos themselves, for example to compare a job's before and after.

Monitoring

Dashboards, alerts, scheduled reports, the activity feed and usage.

Automation operations

Run a rule, retry or dismiss a failed run, and decide approvals (named approvers only).

Write, with undo

Every change is proposed, confirmed by a person, and can be undone. CSV import and export, record history and restoring deleted records.

Build

Apps, tables, automations, voice and text agents, and document templates, built as drafts in a sandbox copy of your workspace and promoted to live when you approve.

Guardrails

Your AI proposes. A person confirms.

Built for operations with branches, teams and an IT review, not a single login.

Nothing changes on one call

Every write, send or action is a proposal the user confirms within 30 minutes. Writes can be undone. More than 5 rows needs bulk permission, and more than 1,000 is refused.

Keys scoped like API keys

Limit a key to certain tables, certain rows ("only the North region's jobs"), hidden columns, insert/update/delete, and an expiry from 1 hour to 90 days. Postgres enforces the row limits.

Builds save as drafts

Apps and automations are checked against the database before they save, new automations and agents are saved switched off, and public apps are never changed.

Sends are limited

Email goes only from the user's own mailbox, at most 20 sends an hour per key, inside the workspace's quiet hours. A sandbox never sends.

Everything is logged

Every call is written to an audit log with the tool, key, person and outcome. Administrators see every key and connected app, and revoking one applies on the next request.

FAQ

Questions

Can ChatGPT or Claude run dispatch for a plumbing company?
Connected through MCP, ChatGPT and Claude can answer from your live plumbing jobs and do the work: re-route emergency call-outs, follow up on open quotes and find completed work that was never invoiced. Fieldproxy's MCP server asks you to confirm every change and can undo it.
Can Microsoft Copilot and Teams work with plumbing job data?
Yes. Add Fieldproxy's MCP server as a tool in a Copilot Studio agent and publish it to Teams and Microsoft 365 Copilot. Each person signs in with their own Fieldproxy account.
Will the AI change jobs or message customers on its own?
No. Every write, send or action is proposed first and saved only after a person confirms. Writes can be undone, and email goes only from the user's own mailbox.

Your plumbing operation, run from chat