# Service Fusion MCP connector

The Service Fusion connector brings customers, jobs, estimates, invoices, crews and calendar tasks to Claude, ChatGPT, Cursor and Microsoft Copilot through one governed endpoint, where every person signs in as themselves and every call is logged.

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

## Facts

| | |
| --- | --- |
| Application | Service Fusion |
| Category | CRM |
| AI tools | 30 |
| Authentication | Connects over OAuth |
| 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 Service Fusion is connected

- Which crews have availability on Thursday morning?
- List open jobs still in scheduled status this week
- Create an estimate for the Miller water heater replacement

## Connect Service Fusion in Elaichi

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

1. Open Connections, choose Add connection, and pick Service Fusion.
2. Optionally set Share with, then press Connect.
3. Supply your own Service Fusion app, then approve. Service Fusion 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 Service Fusion tools are exposed, rename them, or freeze arguments before anyone points a client at it.

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

## Service Fusion 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`.

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

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

## Service Fusion 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 Service Fusion 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 Service Fusion 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 Service Fusion through Elaichi

### Find an open crew for tomorrow morning

Dispatch. Ask which crews have availability tomorrow and what calendar tasks are already on the board before you promise a customer a time window.

### Set up the customer and job after a call

Office. Take the phone call, then have the agent create the customer record and the job with the right job category so nothing waits on retyping.

### Draft an estimate while the lead is warm

Sales. Create an estimate for a new customer from the notes you took on site, then pull it back up to check the details before you send it.

### Review outstanding invoices before month end

Finance. List invoices, see which payment types customers are using, and get a plain summary of what is still open without clicking into each one.

### Know the equipment before the truck rolls

Field service. Pull up the customer equipment on file and the job details so the technician arrives already knowing the unit and what was installed before.

### See where every job stands today

Operations. Ask for jobs grouped by job status to spot what is stuck, what is scheduled and what is ready to invoice.

## Elaichi vs Zapier MCP vs Composio for Service Fusion

All three can connect Service Fusion 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 Service Fusion tools | Allow or restrict single Service Fusion 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 Service Fusion 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 Service Fusion to Claude?

Two steps. First, connect Service Fusion in Elaichi: Service Fusion connects over OAuth, and because Service Fusion asks each company to register its own OAuth application, somebody on your side brings a client ID and secret from Service Fusion once, after which everyone else simply signs in as themselves. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi and you are done.

### Does Service Fusion work with ChatGPT and Cursor as well as Claude?

Yes. Once Service Fusion is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Service Fusion once and every client picks it up.

### What can an AI agent actually do with my Service Fusion data?

With Service Fusion connected, an agent can look up customers, jobs, estimates, invoices, crews, customer equipment, calendar tasks, availability, job statuses, job categories and payment types, and it can create new customers, estimates and jobs. So you can ask which crews are free Thursday, what a customer owes, or have it set up a job after a call. Short, concrete asks such as "open jobs this week" work better than long sentences.

### Does connecting Service Fusion give the AI access to every customer and job?

Only what the person who signed in can already see in Service Fusion. Every call runs inside that person's own Service Fusion access, so a technician and an office manager get different answers to the same question. Elaichi can narrow that access further with restrictions, and it can never widen it.

### Can my team share one Service Fusion connection?

Yes. One person connects Service Fusion in Elaichi and shares it with a team, and nobody else ever handles the client ID or secret. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every Service Fusion call.

### Can I stop an agent from creating or changing things in Service Fusion?

Yes. This Service Fusion connector can read records and create customers, estimates and jobs, and you can restrict any of those create actions on a role or on one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Service Fusion connection when someone leaves?

Offboarding that person in Elaichi ends their access to Service Fusion through every client at once. A shared Service Fusion connection keeps working for everyone else on the team. If you want to remove Service Fusion entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.

### Does the Service Fusion MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Service Fusion 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 Service Fusion?

Yes. Both let Claude, ChatGPT or Cursor use Service Fusion. 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 Service Fusion call.

### How is Elaichi different from Composio for Service Fusion?

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 Service Fusion: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 30 Service Fusion tools

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

- **List all Service Fusion availability** (List). GET /availability (GET /v1/availability). List available time slots for technicians and crews. Requires Workforce Management view permission when `filters[scope]` is `techs` or `all`, and Crew Management view permission when `filters[scope]` is `crews` or `all`. The connector pages with page / per_page (limit = page size, at most 100) while _meta.currentPage &lt; pageCount. Filters use underscore names (filters_x_y), sent as Service Fusion's bracket keys (filters[x][y]). Lists (filters_departments) are sent as repeated bracket keys. Required: filters_period_start_date, filters_period_end_date.
- **List all Service Fusion calendar tasks** (List). GET /calendar-tasks (GET /v1/calendar-tasks). List all CalendarTasks matching query criteria, if provided, otherwise list all CalendarTasks. The connector pages with page / per-page (limit = page size, at most 50) while _meta.currentPage &lt; pageCount. Filters use underscore names (filters_x_y), sent as Service Fusion's bracket keys (filters[x][y]).
- **Get single Service Fusion calendar task by ID** (Get). GET /calendar-tasks/{calendar-task-id} (GET /v1/calendar-tasks/{calendar-task-id}). Get a CalendarTask by identifier. Required: id.
- **List all Service Fusion crews** (List). GET /crews (GET /v1/crews). List all Crews matching query criteria, if provided, otherwise list all Crews. The connector pages with page / per-page (limit = page size, at most 50) while _meta.currentPage &lt; pageCount.
- **Get single Service Fusion crew by ID** (Get). GET /crews/{crew-id} (GET /v1/crews/{crew-id}). Get a Crew by identifier. Required: id.
- **List all Service Fusion customer equipment** (List). GET /customers/{customer-id}/equipment (GET /v1/customers/{customer-id}/equipment). List all Equipment matching query criteria, if provided, otherwise list all Equipment. The connector pages with page / per-page (limit = page size, at most 50) while _meta.currentPage &lt; pageCount. Required: customer_id.
- **Get single Service Fusion customer equipment by ID** (Get). GET /customers/{customer-id}/equipment/{equipment-id} (GET /v1/customers/{customer-id}/equipment/{equipment-id}). Get a Equipment by identifier. Required: id, customer_id.
- **Create a Service Fusion customer** (Create). POST /customers (POST /v1/customers). Create a new Customer. Required: customer_name.
- **List all Service Fusion customers** (List). GET /customers (GET /v1/customers). List all Customers matching query criteria, if provided, otherwise list all Customers. The connector pages with page / per-page (limit = page size, at most 50) while _meta.currentPage &lt; pageCount. Filters use underscore names (filters_x_y), sent as Service Fusion's bracket keys (filters[x][y]).
- **Get single Service Fusion customer by ID** (Get). GET /customers/{customer-id} (GET /v1/customers/{customer-id}). Get a Customer by identifier. Required: id.
- **Create a Service Fusion estimate** (Create). POST /estimates (POST /v1/estimates). Create a new Estimate. Required: customer_name.
- **List all Service Fusion estimates** (List). GET /estimates (GET /v1/estimates). List all Estimates matching query criteria, if provided, otherwise list all Estimates. The connector pages with page / per-page (limit = page size, at most 50) while _meta.currentPage &lt; pageCount. Filters use underscore names (filters_x_y), sent as Service Fusion's bracket keys (filters[x][y]).
- **Get single Service Fusion estimate by ID** (Get). GET /estimates/{estimate-id} (GET /v1/estimates/{estimate-id}). Get a Estimate by identifier. Required: id.
- **List all Service Fusion invoices** (List). GET /invoices (GET /v1/invoices). List all Invoices matching query criteria, if provided, otherwise list all Invoices. The connector pages with page / per-page (limit = page size, at most 50) while _meta.currentPage &lt; pageCount.
- **Get single Service Fusion invoice by ID** (Get). GET /invoices/{invoice-id} (GET /v1/invoices/{invoice-id}). Get a Invoice by identifier. Required: id.
- **List all Service Fusion job categories** (List). GET /job-categories (GET /v1/job-categories). List all JobCategories matching query criteria, if provided, otherwise list all JobCategories. The connector pages with page / per-page (limit = page size, at most 50) while _meta.currentPage &lt; pageCount.
- **Get single Service Fusion job category by ID** (Get). GET /job-categories/{job-category-id} (GET /v1/job-categories/{job-category-id}). Get a JobCategory by identifier. Required: id.
- **List all Service Fusion job statuses** (List). GET /job-statuses (GET /v1/job-statuses). List all JobStatuses matching query criteria, if provided, otherwise list all JobStatuses. The connector pages with page / per-page (limit = page size, at most 50) while _meta.currentPage &lt; pageCount.
- **Get single Service Fusion job status by ID** (Get). GET /job-statuses/{job-status-id} (GET /v1/job-statuses/{job-status-id}). Get a JobStatus by identifier. Required: id.
- **Create a Service Fusion job** (Create). POST /jobs (POST /v1/jobs). Create a new Job. Required: customer_name.
- **List all Service Fusion jobs** (List). GET /jobs (GET /v1/jobs). List all Jobs matching query criteria, if provided, otherwise list all Jobs. The connector pages with page / per-page (limit = page size, at most 50) while _meta.currentPage &lt; pageCount. Filters use underscore names (filters_x_y), sent as Service Fusion's bracket keys (filters[x][y]).
- **Get single Service Fusion job by ID** (Get). GET /jobs/{job-id} (GET /v1/jobs/{job-id}). Get a Job by identifier. Required: id.
- **List all Service Fusion me** (List). GET /me (GET /v1/me). Authorized user information.
- **List all Service Fusion payment types** (List). GET /payment-types (GET /v1/payment-types). List all PaymentTypes matching query criteria, if provided, otherwise list all PaymentTypes. The connector pages with page / per-page (limit = page size, at most 50) while _meta.currentPage &lt; pageCount.
- **Get single Service Fusion payment type by ID** (Get). GET /payment-types/{payment-type-id} (GET /v1/payment-types/{payment-type-id}). Get a PaymentType by identifier. Required: id.
- **List all Service Fusion sources** (List). GET /sources (GET /v1/sources). List all Sources matching query criteria, if provided, otherwise list all Sources. The connector pages with page / per-page (limit = page size, at most 50) while _meta.currentPage &lt; pageCount.
- **Get single Service Fusion source by ID** (Get). GET /sources/{source-id} (GET /v1/sources/{source-id}). Get a Source by identifier. Required: id.
- **List all Service Fusion tech departments** (List). GET /techs/departments (GET /v1/techs/departments). Returns a flat list of Departments values.
- **List all Service Fusion techs** (List). GET /techs (GET /v1/techs). List all Techs matching query criteria, if provided, otherwise list all Techs. The connector pages with page / per-page (limit = page size, at most 50) while _meta.currentPage &lt; pageCount. Filters use underscore names (filters_x_y), sent as Service Fusion's bracket keys (filters[x][y]).
- **Get single Service Fusion tech by ID** (Get). GET /techs/{tech-id} (GET /v1/techs/{tech-id}). Get a Tech by identifier. Required: id.
