ServiceM8 MCP connector
The ServiceM8 connector brings jobs, clients, bookings and allocation windows into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person works on live ServiceM8 records as themselves, with every call logged.
- OAuth or API key
- Free 14-day trial
- No credit card
Which jobs are booked for tomorrow and who is assigned to each?
Working in ServiceM8 with Elaichi
-
Get single ServiceM8 addon account key value by ID
-
List all ServiceM8 addon account key values
-
Get single ServiceM8 addon deployment by ID
How to connect ServiceM8 to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
ServiceM8 MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
ServiceM8 MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
ServiceM8 MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
ServiceM8 MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
ServiceM8 MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect ServiceM8 to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with ServiceM8 through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in ServiceM8 is logged.
-
Office
Catch the job up after the call
A customer rings to change the access instructions or add a second task. Tell the agent what changed and the ServiceM8 job is updated with a note before the next call comes in.
-
Dispatch
Find a gap and book the job
Ask which allocation windows are still open on Thursday and who is free, then book the job into the right slot without flicking between the calendar and the job list.
-
Field
Pull up the job before you knock
On the way to site, ask for the address, the contact, the notes from the last visit and what was quoted, all from the live ServiceM8 job.
-
Sales
Turn an inquiry into a quoted job
Give the agent the caller's details and the work they described. It creates the client if they are new, raises the job in ServiceM8 and leaves it ready for pricing.
-
Accounts
Chase what is finished but not invoiced
Ask for every ServiceM8 job marked complete this week that still has no invoice, so nothing done on site is forgotten at month end.
-
Management
See how the week actually went
Ask how many jobs each staff member completed, which clients booked repeat work and where jobs are stuck, straight from ServiceM8 rather than a spreadsheet someone built on Friday.
Try asking
- “Which jobs are booked for tomorrow and who is assigned to each?”
- “Add a note to the Harbor Street job: customer wants a call first”
- “Find clients with no job in the last six months”
What connecting ServiceM8 gets you
6 screens from Elaichi, each doing one job for your ServiceM8 account.
Ask Elaichi to work across your apps.
Which jobs are booked for tomorrow and who is assigned to each?
Add a note to the Harbor Street job: customer wants a call first
Find clients with no job in the last six months
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about today's jobs in plain words.
Which jobs are unassigned tomorrow, answered from live ServiceM8 records, not a stale export.
Copy the endpoint
AI apps
One ServiceM8 endpoint for every AI client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
Tool catalog
243 ServiceM8 tools, no custom code.
Jobs, clients, allocation windows and addons, each with the methods your team actually uses.
Toolboxes
Each team gets its own ServiceM8 toolbox.
Dispatch sees scheduling, accounts sees completed jobs, nobody carries tools they do not need.
Shared connections
Teammates work in ServiceM8 without the credential.
One person connects, shares with a team, and nobody else ever sees a key.
Audit log
Every ServiceM8 call lands in the log.
When, who, what happened and which job, answered without asking around the office.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
ServiceM8 digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch jobs
ServiceM8
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
ServiceM8
Queued
Workflows
A schedule starts ServiceM8 work end to end.
Completed jobs are fetched, grouped and drafted into a digest, approved, then posted back.
ServiceM8 health
Refreshed 4 minutes ago · every 15 minutes · from the jobs collection
Jobs
1,284 ↓ 12%
Clients
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Jobs created
Last 14 days
By team
Share of activity
Head office 34%
Dispatch 27%
Plumbing crew 21%
Electrical crew 18%
Collections and dashboards
ServiceM8 health, computed on a schedule.
Jobs created over 14 days, split by team, counted from records with no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for ServiceM8
All three can connect ServiceM8 to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over ServiceM8 tools | Allow or restrict single ServiceM8 tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per ServiceM8 call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
ServiceM8 tools for your AI agents
243 tools are ready to call through Elaichi's MCP endpoint the moment you connect ServiceM8, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect ServiceM8 to Claude?
First connect ServiceM8 in Elaichi. ServiceM8 asks you to register an OAuth application inside your own ServiceM8 account, so one person brings that client ID and secret to Elaichi once, or pastes a ServiceM8 API key instead if that is easier. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Each person signs in to ServiceM8 as themselves from there, and nobody has to repeat the setup.
Does ServiceM8 work with ChatGPT and Cursor as well as Claude?
Yes. ServiceM8 is connected once in Elaichi and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. There is nothing separate to set up per client.
What can an AI agent actually do with my ServiceM8 data?
It can look up and update ServiceM8 jobs and clients, add notes, check which allocation windows are open and book work into them, and tell you which jobs are complete, unassigned or waiting on someone. The agent does not see a list of hundreds of operations. It searches for the right one and runs it, so short concrete asks like "book the Harbor Street job for Tuesday morning" work better than long paragraphs.
Does connecting ServiceM8 give the AI access to every job and client?
No. The agent only sees what the person who signed in to ServiceM8 can already see, so a field staff member with limited job access gets exactly that and no more. Elaichi can narrow access further with restrictions, and it never widens what ServiceM8 itself allows.
Can I stop an agent from deleting or changing things in ServiceM8?
Yes. Restrictions apply per action, so you can restrict deleting ServiceM8 jobs or editing allocation windows for a role or for one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it no matter how the prompt is worded.
What happens to a ServiceM8 connection when someone leaves?
Offboarding that person in Elaichi ends their access to ServiceM8 through every client at once. A shared ServiceM8 connection keeps working for everyone else on the team. If you want ServiceM8 gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.
Does the ServiceM8 MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. ServiceM8 is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for ServiceM8?
Yes. Both let Claude, ChatGPT or Cursor use ServiceM8. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every ServiceM8 call.
How is Elaichi different from Composio for ServiceM8?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to ServiceM8: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put ServiceM8 in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot