# Connect ServiceM8 to Claude Prepare a grounded field-service job briefing

> Read jobs with Claude and Agent200. Prepare a field-service job briefing using the connected user’s own ServiceM8 account.

- Page: https://www.agent200.com/connectors/servicem8/framework/claude/
- Connector: [ServiceM8](https://www.agent200.com/connectors/servicem8.md)
- Framework: Claude
- Updated: 2026-11-17

## Instructions for AI agents

Goal: connect ServiceM8 to Claude with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/servicem8/framework/claude/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Claude's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure ServiceM8 is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Claude: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Claude's exact menus or commands.
4. The first ServiceM8 request returns an authorization link if the user has not connected ServiceM8 yet: show it to them and continue once they have approved access on ServiceM8's own page.
5. Check it works with this request: "Read the ServiceM8 job I identify. Include its returned status, client and scheduled activities. Cite the specific records and disclose missing fields. Do not edit jobs or message anyone."
   What should come back:
   - The selected job is identified.
   - Only returned job status, client identity and scheduled activity details actually returned are reported.
   - Access gaps and missing context are explicit; no source data is changed.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in ServiceM8, then retry.

## Overview

Ask Claude for a focused field-service job briefing from one selected job. Compare its answer with the retrieved source and separate suggestions from recorded facts.

Start with one identified job. Preserve returned job status, client identity and scheduled activity details actually returned; report missing data and keep the workflow read-only.

Provider reference: [ServiceM8 API](https://developer.servicem8.com/reference/listjobs).

- **Connector:** [ServiceM8](https://www.agent200.com/connectors/servicem8/)
- **Works with:** Claude · Agent app, through MCP
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [6 tools](https://www.agent200.com/connectors/servicem8/framework/claude/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **ServiceM8 enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **An end user with a ServiceM8 account.** They approve access once, on ServiceM8's own page.
- **Claude, with custom MCP servers allowed.** Custom connectors are on every Claude plan (Free: one). Sending an API key uses the Request headers option, a beta that only some accounts have; on Team and Enterprise an Owner adds the connector for everyone.

## Connect ServiceM8 to Claude

### Step 1: Create your Agent200 API key

Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Claude in the next step, as "Authorization: Bearer <your key>". One key covers ServiceM8 and every other connector enabled for your project. Keep it out of chats and source control.

Create an API key: https://agent200.com/platform/apikeys/

### Step 2: Open Connectors in Claude

On a Free, Pro, Max or Ultra plan, go to **Customize > Connectors**. On Team or Enterprise, an Owner goes to **Organization settings > Connectors**; members then find the connector under Customize > Connectors.

### Step 3: Add a custom connector

Select **Add**, then **Add custom connector**. Enter a name, Agent200, and the remote MCP server URL, then choose **Continue**.

### Step 4: Send your key as a request header

Under Authentication choose **No sign-in**. Open **Request headers**, pick `authorization`, enter `Bearer` followed by a space and your key, mark it Required and choose **Add**. Claude sends the value exactly as typed.

File `Add custom connector`:

```text
Remote MCP server URL:  https://api.agent200.com/mcp/
Authentication:         No sign-in
Request header name:    authorization
Value:                  Bearer YOUR_AGENT200_API_KEY
```

### Step 5: Turn it on in a chat

In a chat, select **+ > Connectors** and turn Agent200 on. Ask Claude to list the Agent200 tools to check the connection; Claude asks before a tool runs the first time.

### Step 6: Connect your ServiceM8 account

The first time you ask Claude for something in ServiceM8, Agent200 returns an authorization link. Open it and approve access on ServiceM8's own page. Agent200 stores the connection and keeps it working; your password never reaches Claude or Agent200.

## Test your connection

Ask: "Read the ServiceM8 job I identify. Include its returned status, client and scheduled activities. Cite the specific records and disclose missing fields. Do not edit jobs or message anyone."

What should come back:

- The selected job is identified.
- Only returned job status, client identity and scheduled activity details actually returned are reported.
- Access gaps and missing context are explicit; no source data is changed.

Check the job and client UUIDs, connected account, OAuth read scopes and schedule window. Report missing or inaccessible records without assuming that no work is scheduled.

## ServiceM8 tools Claude can call

- **List jobs** (`servicem8_list_jobs`, read): Find accessible jobs and their returned status and client references.
- **Read a job** (`servicem8_get_job`, read): Retrieve details of one identified job.
- **List clients** (`servicem8_list_clients`, read): Find client records available to the connected account.
- **Read a client** (`servicem8_get_client`, read): Retrieve one identified client record.
- **List client contacts** (`servicem8_list_client_contacts`, read): Find contacts associated with an identified client.
- **List scheduled activities** (`servicem8_list_job_activities`, read): Read scheduled job activities within the available scope.

## How it works

1. **You ask Claude.** In your own words, for something in ServiceM8.
2. **Claude picks a tool.** It sees the ServiceM8 tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** With your own ServiceM8 connection, within the tools and scopes your project allows.
4. **Claude answers.** It gets the result back from the MCP server and uses it in its reply or its next step.

**Each user's own connection.** Connections belong to individual end users. A request for one user never reaches another user's ServiceM8 account.

**Permissions at every level.** Your project settings decide what the agent may request, the end user decides what they authorize, and ServiceM8 enforces what its API grants.

## Troubleshooting

### The source cannot be read

Check the job and client UUIDs, connected account, OAuth read scopes and schedule window. Report missing or inaccessible records without assuming that no work is scheduled.

## FAQ

### How do I verify this result?

Compare the named job and returned job status, client identity and scheduled activity details actually returned with the source. Treat missing information as missing, not as a fact.

## Use ServiceM8 with another framework

- [ServiceM8 + ChatGPT](https://www.agent200.com/connectors/servicem8/framework/chatgpt.md)
- [ServiceM8 + Claude Code](https://www.agent200.com/connectors/servicem8/framework/claude-code.md)
- [ServiceM8 + Muse](https://www.agent200.com/connectors/servicem8/framework/muse.md)
- [ServiceM8 + Grok Bot](https://www.agent200.com/connectors/servicem8/framework/grok-bot.md)
- [ServiceM8 + OpenAI Dots](https://www.agent200.com/connectors/servicem8/framework/openai-dots.md)
- [ServiceM8 + Claude Duet](https://www.agent200.com/connectors/servicem8/framework/claude-duet.md)
- [ServiceM8 + Hermes Agent](https://www.agent200.com/connectors/servicem8/framework/hermes-agent.md)
- [ServiceM8 + OpenClaw](https://www.agent200.com/connectors/servicem8/framework/openclaw.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
