I’m trying to connect my ServiceM8 account to Claude using your MCP integration (developer.servicem8.com/mcp), added as a custom connector under Claude’s Settings → Connectors.
The initial connection request succeeds and I’m redirected to ServiceM8 to log in and authorize. After logging in, I land on a ServiceM8-branded 500 Internal Server Error page (“Something went wrong on our end… Our team has been notified”). This has reproduced identically on two separate attempts.
This looks related to an existing thread on your developer forum (“Super Excited About MCP Support!”) where another user reported a different failure (404 on client registration) connecting Claude to this same MCP endpoint; possibly the same underlying issue in the OAuth authorization flow.
Could you check the server logs around this authorization step and let me know when it’s resolved?
Hi Inno, sorry for the trouble. We traced your failed attempts to a ServiceM8 issue rendering the authorization page after login. Your account is now running a version containing the fix. Please try connecting Claude again. If it still fails, share the approximate time and timezone of the attempt so we can trace it.
The documented Claude setup is to add a custom connector in Claude and use https://api.servicem8.com/mcp as the ServiceM8 MCP server URL, then sign in and authorize access if prompted.
If you used a different URL, try removing and re-adding the custom connector with that exact URL first.
For the 500 error after ServiceM8 sign-in/authorization, we’ll need to trace the exact request privately, so email support@servicem8.com with the exact date, time and timezone of the latest attempt, plus the full error text and authorization URL shown in the browser.