# 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.

Source: https://elaichi.ai/connectors/servicem8/

## Facts

| | |
| --- | --- |
| Application | ServiceM8 |
| Category | CRM |
| AI tools | 243 |
| Authentication | OAuth or API key |
| Bring your own OAuth app | Yes |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once ServiceM8 is connected

- 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

## Connect ServiceM8 in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick ServiceM8.
2. Optionally set Share with, then press Connect.
3. Supply your own ServiceM8 app, then approve. ServiceM8 needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which ServiceM8 tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## ServiceM8 MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## ServiceM8 MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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.
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.

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a ServiceM8 tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with ServiceM8 through Elaichi

### Catch the job up after the call

Office. 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.

### Find a gap and book the job

Dispatch. 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.

### Pull up the job before you knock

Field. 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.

### Turn an inquiry into a quoted job

Sales. 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.

### Chase what is finished but not invoiced

Accounts. Ask for every ServiceM8 job marked complete this week that still has no invoice, so nothing done on site is forgotten at month end.

### See how the week actually went

Management. 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.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one ServiceM8 connection?

Yes. One person connects ServiceM8 and shares the connection with a team, and nobody else ever handles the client secret or an API key. Each person still signs in to Elaichi as themselves, so the audit log names who booked the job or edited the client, not a shared account.

### 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.

## All 243 ServiceM8 tools

Every tool below is callable through https://api.elaichi.ai/mcp once ServiceM8 is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a ServiceM8 account provision** (Create). Provision a new ServiceM8 account. Use this endpoint to create a new ServiceM8 account programatically. Specify the request parameters as a JSON object in the body of the request. Required: country, demo, business_name, email. ServiceM8 Partner accounts only.
- **Delete a ServiceM8 addon account key value by ID** (Delete). Delete one key for an account. Deletes a single key stored by your Addon against the authenticated account. Required: id. Needs an OAuth connection (ServiceM8 limits it to public add-ons); with an API key ServiceM8 returns an error.
- **Get single ServiceM8 addon account key value by ID** (Get). Get one key for an account. Returns the value of a single key stored by your Addon against the authenticated account. Required: id. Needs an OAuth connection (ServiceM8 limits it to public add-ons); with an API key ServiceM8 returns an error.
- **Update a ServiceM8 addon account key value by ID** (Update). Set one key for an account. Sets the value of a single key stored by your Addon against the authenticated account. Creates the key if it does not exist, or replaces the existing value. The request is rejected with a 413 response if the update would take the total storage for the account over the 64KB limit. Required: id, value. Needs an OAuth connection (ServiceM8 limits it to public add-ons); with an API key ServiceM8 returns an error.
- **List all ServiceM8 addon account key values** (List). List all keys for an account. Returns all keys and values stored by your Addon against the authenticated account. Needs an OAuth connection (ServiceM8 limits it to public add-ons); with an API key ServiceM8 returns an error.
- **Get single ServiceM8 addon deployment by ID** (Get). Poll deployment status. Required: id, addon_slug. API-key connections only (the add-on developer's own key).
- **List all ServiceM8 addon identities** (List). Identify the authenticated account. Returns the ServiceM8 account the presented API key belongs to, and the key's access level. Used by developer tooling (the sm8 CLI) to validate credentials. API-key connections only (the add-on developer's own key).
- **Delete a ServiceM8 addon job key value by ID** (Delete). Delete one key for a job. Deletes a single key stored by your Addon against the given job. OAuth scope: manage_jobs or manage_addon_storage (either is sufficient). Required: id, job_id. Needs an OAuth connection (ServiceM8 limits it to public add-ons); with an API key ServiceM8 returns an error.
- **Get single ServiceM8 addon job key value by ID** (Get). Get one key for a job. Returns the value of a single key stored by your Addon against the given job. OAuth scope: read_jobs or read_addon_storage (either is sufficient). Required: id, job_id. Needs an OAuth connection (ServiceM8 limits it to public add-ons); with an API key ServiceM8 returns an error.
- **Update a ServiceM8 addon job key value by ID** (Update). Set one key for a job. Sets the value of a single key stored by your Addon against the given job. Creates the key if it does not exist, or replaces the existing value. The request is rejected with a 413 response if the update would take the total storage for the job over the 64KB limit. Required: id, job_id, value. Needs an OAuth connection (ServiceM8 limits it to public add-ons); with an API key ServiceM8 returns an error.
- **List all ServiceM8 addon job key values** (List). List all keys for a job. Returns all keys and values stored by your Addon against the given job. OAuth scope: read_jobs or read_addon_storage (either is sufficient). Required: job_id. Needs an OAuth connection (ServiceM8 limits it to public add-ons); with an API key ServiceM8 returns an error.
- **Create a ServiceM8 addon log session** (Create). Stream live logs for one add-on over SSE. Authenticates the developer and proxies CloudWatch Live Tail over SSE. AWS credentials remain server-side. Requires manage_addons or a full-access API key and Accept: text/event-stream. Required: addon_slug.
- **List all ServiceM8 addon manifest schemas** (List). Get the add-on manifest v1 JSON Schema. Public, read-only JSON Schema for documentation and editor validation. Returns the same Draft 7 schema used by ServiceM8 manifest validation, without a response envelope. No API key, OAuth token or feature flag is required.
- **Delete a ServiceM8 addon secret by ID** (Delete). Delete a secret. Required: id, addon_slug. API-key connections only (the add-on developer's own key).
- **Update a ServiceM8 addon secret by ID** (Update). Set a secret. Secrets are delivered to the add-on's function as environment variables and applied immediately - no redeploy required. Names are case-insensitive and canonicalized to UPPER_CASE. Requires a full-access API key. Required: id, addon_slug, value. API-key connections only (the add-on developer's own key).
- **List all ServiceM8 addon secrets** (List). List secret names for an add-on. Names only - values are never returned. Requires a full-access API key. Required: addon_slug. API-key connections only (the add-on developer's own key).
- **Update a ServiceM8 addon by ID** (Update). Deploy an add-on (atomic manifest + function upsert). Creates the add-on on first deploy (private/unlisted) and updates it thereafter. One multipart request carries the manifest JSON part and the bundled function source part. The manifest is validated before anything is committed. Returns 202 with a deployment id to poll. Required: id, manifest, function. API-key connections only (the add-on developer's own key).
- **Get single ServiceM8 addon by ID** (Get). Fetch one add-on by slug. Required: id. API-key connections only (the add-on developer's own key).
- **List all ServiceM8 addons** (List). List the account's add-ons. API-key connections only (the add-on developer's own key).
- **Create a ServiceM8 allocation window** (Create). Create a new Allocation Window. OAuth scope: manage_schedule. ServiceM8 returns the new record's UUID in the x-record-uuid response header; or send your own uuid in the body.
- **List all ServiceM8 allocation windows** (List). List all Allocation Windows. OAuth scope: read_schedule. The connector pages through all results (up to 1,000 per page).
- **Delete a ServiceM8 allocation window by ID** (Delete). Delete an Allocation Window. In ServiceM8, deleting a record sets its active field to 0. Inactive records are still accessible on the API, but are hidden in the UI. Inactive records can be restored by setting their active field to 1. OAuth scope: manage_schedule. Required: id.
- **Get single ServiceM8 allocation window by ID** (Get). Retrieve an Allocation Window. OAuth scope: read_schedule. Required: id.
- **Update a ServiceM8 allocation window by ID** (Update). Update an Allocation Window. OAuth scope: manage_schedule. Required: id.
- **Create a ServiceM8 asset type field** (Create). Create a new Asset Type Field. OAuth scope: manage_assets. Required: name. ServiceM8 returns the new record's UUID in the x-record-uuid response header; or send your own uuid in the body.
- **List all ServiceM8 asset type fields** (List). List all Asset Type Fields. OAuth scope: read_assets. The connector pages through all results (up to 1,000 per page).
- **Delete a ServiceM8 asset type field by ID** (Delete). Delete an Asset Type Field. In ServiceM8, deleting a record sets its active field to 0. Inactive records are still accessible on the API, but are hidden in the UI. Inactive records can be restored by setting their active field to 1. OAuth scope: manage_assets. Required: id.
- **Get single ServiceM8 asset type field by ID** (Get). Retrieve an Asset Type Field. OAuth scope: read_assets. Required: id.
- **Update a ServiceM8 asset type field by ID** (Update). Update an Asset Type Field. OAuth scope: manage_assets. Required: id.
- **Create a ServiceM8 asset type** (Create). Create a new Asset Type. OAuth scope: manage_assets. ServiceM8 returns the new record's UUID in the x-record-uuid response header; or send your own uuid in the body.
- **List all ServiceM8 asset types** (List). List all Asset Types. OAuth scope: read_assets. The connector pages through all results (up to 1,000 per page).
- **Delete a ServiceM8 asset type by ID** (Delete). Delete an Asset Type. In ServiceM8, deleting a record sets its active field to 0. Inactive records are still accessible on the API, but are hidden in the UI. Inactive records can be restored by setting their active field to 1. OAuth scope: manage_assets. Required: id.
- **Get single ServiceM8 asset type by ID** (Get). Retrieve an Asset Type. OAuth scope: read_assets. Required: id.
- **Update a ServiceM8 asset type by ID** (Update). Update an Asset Type. OAuth scope: manage_assets. Required: id.
- **Delete a ServiceM8 asset by ID** (Delete). Delete an Asset. In ServiceM8, deleting a record sets its active field to 0. Inactive records are still accessible on the API, but are hidden in the UI. Inactive records can be restored by setting their active field to 1. OAuth scope: manage_assets. Required: id.
- **Get single ServiceM8 asset by ID** (Get). Retrieve an Asset. OAuth scope: read_assets. Required: id.
- **Update a ServiceM8 asset by ID** (Update). Update an Asset. OAuth scope: manage_assets. Required: id.
- **List all ServiceM8 assets** (List). List all Assets. OAuth scope: read_assets. The connector pages through all results (up to 1,000 per page).
- **List all ServiceM8 attachment files** (List). Download an Attachment file. Retrieve the binary file associated with an Attachment. Authenticate the API request with an API key or an OAuth token with read_attachments. The API returns a 302 redirect; follow the Location header to retrieve the file bytes from storage. Required: attachment_id.
- **Create a ServiceM8 attachment** (Create). Create a new Attachment. OAuth scope: manage_attachments. Required: file, related_object, related_object_uuid. Sends the file and its metadata in one multipart request (ServiceM8's recommended upload; the legacy raw upload to /attachment/{uuid}.file isn't available through the connector). ServiceM8 returns the new record's UUID in the x-record-uuid response header; or send your own uuid in the body.
- **List all ServiceM8 attachments** (List). List all Attachments. OAuth scope: read_attachments. The connector pages through all results (up to 1,000 per page).
- **Delete a ServiceM8 attachment by ID** (Delete). Delete an Attachment. In ServiceM8, deleting a record sets its active field to 0. Inactive records are still accessible on the API, but are hidden in the UI. Inactive records can be restored by setting their active field to 1. OAuth scope: manage_attachments. Required: id.
- **Get single ServiceM8 attachment by ID** (Get). Retrieve an Attachment. OAuth scope: read_attachments. Required: id.
- **Update a ServiceM8 attachment by ID** (Update). Update an Attachment. OAuth scope: manage_attachments. Required: id.
- **Create a ServiceM8 availability** (Create). Create a new Availability. OAuth scope: manage_schedule. ServiceM8 returns the new record's UUID in the x-record-uuid response header; or send your own uuid in the body.
- **List all ServiceM8 availabilities** (List). List all Availabilities. OAuth scope: read_schedule. The connector pages through all results (up to 1,000 per page).
- **Delete a ServiceM8 availability by ID** (Delete). Delete an Availability. In ServiceM8, deleting a record sets its active field to 0. Inactive records are still accessible on the API, but are hidden in the UI. Inactive records can be restored by setting their active field to 1. OAuth scope: manage_schedule. Required: id.
- **Get single ServiceM8 availability by ID** (Get). Retrieve an Availability. OAuth scope: read_schedule. Required: id.
- **Update a ServiceM8 availability by ID** (Update). Update an Availability. OAuth scope: manage_schedule. Required: id.
- **Create a ServiceM8 badge** (Create). Create a new Badge. OAuth scope: manage_badges. Required: name. ServiceM8 returns the new record's UUID in the x-record-uuid response header; or send your own uuid in the body.
- ...and 193 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
