Job Contact details consistently missing from MCP get_job_details tool since 28 Sept 2026

Hi all,

We use the official ServiceM8 MCP connector (https://api.servicem8.com/mcp) via Claude to pull job details for internal processing. Since late September we’ve seen the get_job_details tool consistently return no contact information (mobile, phone, email) for newly created jobs, even though the same jobs show full contact details when viewed directly in the ServiceM8 app/web interface.

Timing observed:
I started using Claude with no issues from job #2534. From then, all jobs through to job #2564 (created 07:33 BST / 06:33 UTC, 28 Sept 2026) returned full contact details with no problems.
Job #2565 (created 07:40 BST / 06:39 UTC, same day) — contact details missing.
Every job created from that point through to the date of this post (including #2566, 2567, 2569, 2570, 2572, 2575, 2577, 2579, 2580, 2581, 2585, 2589, 2590, 2591, 2592) has had the same problem — contact fields come back empty from the tool, regardless of whether the customer is new or returning.

So the change appears to have started in roughly the 06:33–06:39 UTC window on 28 September 2026.

What we’ve ruled out / confirmed via ServiceM8 Support (ticket #342502):

  • Not a caching/staleness issue — re-querying hours later still shows other fields (description, status) updating correctly, but contact fields stay empty.
  • Not specific to new vs. existing customers — it also affects jobs for customers with contact details already on file from previous jobs.
  • Support has confirmed this isn’t a known/documented issue on their side, and pointed us here since diagnosing it needs visibility into which resource(s) the MCP tool requests (e.g. whether it’s querying the Job Contact record, /jobcontact.json) and whether/how it maps the result into its response — something we can’t see from our side, since we only receive the tool’s final JSON output.

Question: Is there a known issue or recent change with how the MCP get_job_details tool requests/returns Job Contact data? Happy to provide further technical details (job UUIDs etc.) if that helps diagnosis, but keeping customer names/contact details out of this public thread for data protection reasons.

Thanks,
Karina

(Note: I’m using Claude to help draft and track these replies, so responses in this thread may come via me after being discussed with Claude — just flagging in case the phrasing looks AI-assisted.)

Hi Karina,

At this stage, we can’t confirm a documented known issue or intended change matching this behaviour. The current MCP documentation confirms that Claude connects through https://api.servicem8.com/mcp and can view detailed job information, but it doesn’t define which underlying resources or contact fields get_job_details returns.

Separately, the REST API documentation shows that /jobcontact.json is the Job Contacts resource, requires the read_job_contacts scope, and includes phone, mobile, and email fields linked by job_uuid. Based on the published documentation alone, we can’t determine whether the missing fields are caused by the underlying Job Contact data or the MCP tool’s response mapping.

Please email support@servicem8.com with the affected job UUIDs and one redacted get_job_details response, quoting ticket #342502, rather than posting those details publicly.

Thanks,
Cody