Short answer
An MCP server is the connection that lets an AI assistant such as Claude, ChatGPT or Microsoft Copilot use a piece of software. MCP, the Model Context Protocol, is an open standard: the software publishes a list of tools ("find jobs", "plan routes", "draft email") and the assistant calls them when you ask for something. For a field service company, an MCP server turns your field service software into something your team can run by asking in plain English, with the permissions you set.
How it works, in one example
You type "Which jobs did we finish last week that nobody invoiced?" into Claude. Claude sees that the Fieldproxy connection has a tool for finding jobs and one for invoices, calls them, and answers from your live data.
If you then ask it to draft reminders, it calls the email tool, which prepares drafts. With Fieldproxy nothing is sent until you confirm.
What to check before connecting one
- Is it official (built by the software vendor) or a community project you host yourself?
- Can it only read, or also act? Which actions?
- Can you limit a connection to certain tables, rows or columns?
- Does a person confirm changes, and can they be undone?
- Is every call logged, and can an administrator revoke access instantly?
Where field service vendors stand
As of September 27, 2026, Fieldproxy, Jobber and ServiceM8 ship official MCP servers; ServiceTitan, Housecall Pro, Simpro and others have community or third-party servers only. See the comparison table for details and sources.
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.