Introducing Fieldproxy MCP: Run the Day, and Change the Software, From ChatGPT, Claude or Copilot
Today, 27 September 2026, we are opening up Fieldproxy's MCP server. It connects the AI assistant your team already uses, whether that is Claude, ChatGPT or Microsoft Copilot in Teams, to your live Fieldproxy workspace. Your team can run the day by asking, and administrators can change the software itself the same way. Every change is shown first and happens only after a person confirms.
Running this manually today?
See how Fieldproxy handles it — a walkthrough on your own workflow, not a canned demo.
Put AI to workWhat your team can do from the chat
- Re-plan a sick technician's day: spread the jobs across qualified technicians nearby, keep every SLA, and draft the customer messages.
- Find the money: completed jobs that were never invoiced, accounts-receivable ageing, and polite reminders for the overdue ones.
- Quotes and proposals from your own templates, and follow-ups on the ones that went quiet.
- Look at job photos and read attached reports before sign-off.
- A daily operations briefing, dashboards, alerts and scheduled reports.
- Customer 360, technician performance, and why last night's automation failed.
There are 145 built-in tools, plus seven ready-made workflows. Every use case, with the exact requests and the tools they call, is on the use-case pages.
The part nobody else does: your AI can change the software
An administrator can ask for a new field, a screen, a table, an automation or a voice or text agent. It is built as a draft in a sandbox copy of your workspace, checked against your database, and goes live only when approved, with rollback. See what you can change.
Other field service tools are starting to connect to AI assistants too, and that is good for the industry. But as of today, the connectors we checked read and edit records: Jobber's creates requests, clients and properties, and ServiceM8's schedules jobs and sends messages. None of them can change the software. The sourced comparison is in which field service software has an MCP server.
Built for operations with an IT review
- Three access levels (read, write, build), and the signed-in person's own role is always the ceiling.
- Keys limited like API keys: by table, by row (one region, one team), hidden columns, and an expiry from 1 hour to 90 days.
- Nothing changes on a single call: every write, send or build is a proposal a person confirms, and writes can be undone.
- Email only from the user's own mailbox, at most 20 sends an hour per key, inside quiet hours.
- Every call logged with the tool, person and outcome, and any key revoked on the next request.
Where it works
Setup guides for Claude, ChatGPT and Microsoft 365 Copilot and Teams, plus GitHub Copilot, Cursor and OpenAI Codex. It is live in five regions: US East, Canada, India, Norway and New Zealand.
AI assistant access is switched on per workspace, and we set it up with you during onboarding. Questions teams ask before they connect are answered in our guides, including whether it is safe.
Run the day, and change the software, from the chat
Or book a demo and we will run your real questions on your own data.
See the MCP server