Jobber MCP
Does Jobber have an MCP server?
What connecting Jobber to Claude or ChatGPT gets you today, and what it looks like when your AI can change the software itself.
Reply to Claude...
Illustration of Fieldproxy's MCP tools inside Claude, ChatGPT and Copilot. Names and data are examples.
Short answer
Does Jobber have an MCP server?
Official connector for Claude and ChatGPT, launched September 25, 2026, on the Core, Connect, Grow and Plus plans. Jobber's connector is built for looking things up and capturing new work: ask about your business, find unbilled work, and turn call notes into requests and clients. Scheduling, quoting and invoicing still happen in Jobber.
Last verified September 27, 2026
Verified September 27, 2026
Jobber in Claude and ChatGPT, side by side
Jobber
Official MCPCan read
- Requests
- Quotes
- Clients
- Properties
- Jobs
- Invoices
Can change
- Create or edit requests
- Create or edit clients
- Create or edit properties
Cannot
- Create or modify jobs, quotes or invoices
- Add, edit or remove schedule items
- Delete or archive records
Fieldproxy
Official MCPCan read
- Customers, jobs, technicians, invoices, quotes and contracts
- AR ageing, technician performance and funnels
- Documents, email threads and job photos
- Read-only SQL on your own schema
Can change, after you confirm
- The software itself: new fields, screens, tables, automations and agents, built in a sandbox
- Plan and apply the dispatch schedule and routes
- Draft and send email and SMS
- Issue proposals, estimates and PDFs
- Any record, with undo
Works in
- Claude, ChatGPT, Microsoft 365 Copilot and Teams, GitHub Copilot, Cursor, Codex
Sources: Jobber Help Center: Connect Jobber to Claude and ChatGPT · Jobber launch announcement (PR Newswire)
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.
Verified September 27, 2026
Every field service tool, compared
| Software | MCP server | AI can change the software | What it is |
|---|---|---|---|
| Fieldproxy | Official MCP | Yes: fields, screens, tables, automations, agents | 145 tools: read, dispatch, comms, documents, photos, monitoring and build. Claude, ChatGPT, Microsoft 365 Copilot and Teams, GitHub Copilot, Cursor, Codex. |
| ServiceTitan | Third-party only | No | No official MCP server. Community-built servers and Zapier's MCP connect through the ServiceTitan API. |
| Jobber | Official MCP | No | Official connector for Claude and ChatGPT, launched September 25, 2026, on the Core, Connect, Grow and Plus plans. |
| ServiceM8 | Official MCP | No | Official hosted MCP server at api.servicem8.com/mcp, for ChatGPT and Claude, with OAuth sign-in. |
| Housecall Pro | Third-party only | No | No official MCP server. Open-source community servers and Zapier's MCP use the Housecall Pro API. |
| Simpro | Third-party only | No | No official MCP server. SyncHub, a third-party data company, offers a simPRO MCP connector. |
| JobNimbus | Third-party only | No | No official MCP server. Community servers and Zapier's MCP use a JobNimbus API key. |
| AccuLynx | Third-party only | No | No official MCP server. A community server brings AccuLynx jobs, contacts and estimates into Claude Desktop and Cursor. |
| Workiz | Third-party only | No | No official MCP server. An open-source server published by a Workiz customer exposes jobs, leads and team data. |
| Service Fusion | Third-party only | No | No official MCP server. Zapier's MCP connects to Service Fusion's Zapier actions. |
| Tradify | None found | No | We found no official or community MCP server for Tradify. |
| FieldPulse | None found | No | We found no official or community MCP server for FieldPulse. |
| BuildOps | None found | No | We found no official or community MCP server for BuildOps. |
FAQ
Jobber and MCP, answered
- Does Jobber have an MCP server?
- Official connector for Claude and ChatGPT, launched September 25, 2026, on the Core, Connect, Grow and Plus plans. Checked September 27, 2026.
- Can I connect Jobber to Claude or ChatGPT?
- Yes. Jobber's own connector works in Claude and ChatGPT. It cannot: create or modify jobs, quotes or invoices; add, edit or remove schedule items; delete or archive records.
- Can Jobber's AI connection customise the software?
- No. The Jobber connections we found read and edit records; none adds fields, screens or automations. Fieldproxy's MCP server can: ask for a new field, screen or automation and it is built as a draft in a sandbox, then goes live when you approve.
- How is Fieldproxy's MCP server different from Jobber's?
- Fieldproxy's official server has 145 tools and can plan and apply the dispatch schedule, draft and send email and SMS after you confirm, issue proposals, read job photos and documents, and build apps and automations in a sandbox. Keys can be limited to certain tables, rows and columns, and it works in Microsoft 365 Copilot and Teams as well as Claude and ChatGPT.
- Can I move from Jobber to Fieldproxy?
- Yes. Fieldproxy moves your Jobber data for you and builds your system on it before anything switches over, so your team keeps working during the move.
Moving on from Jobber?
We move your data for you and build your system on it first, so your AI and your team are ready on day one.