Roofing · Fieldproxy MCP
Run your roofing operation from ChatGPT, Claude or Teams
Your roofing 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.
Reply to Claude...
Illustration of Fieldproxy's MCP tools inside Claude, ChatGPT and Copilot. Names and data are examples.
Short answer
How can a roofing company use ChatGPT, Claude or Copilot?
Roofing contractors connect ChatGPT or Claude to Fieldproxy through MCP so the assistant can check crews, estimates and job photos, reschedule around the weather and follow up on open proposals, with your approval before anything changes.
Last verified September 27, 2026
Real asks
What roofing teams ask it
"Rain is forecast Thursday. Which tear-offs should move, and to when?"
"Which estimates sent this month have not been signed?"
"Show me the drone and site photos for the Parker job."
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
Build a screen
Wire an automation
Create an agent
Add your own tools
Roll back anything
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 roofing company?
- Roofing contractors connect ChatGPT or Claude to Fieldproxy through MCP so the assistant can check crews, estimates and job photos, reschedule around the weather and follow up on open proposals, with your approval before anything changes.
- Can Microsoft Copilot and Teams work with roofing 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.