Skip to content

CRM

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.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

Which crews have availability on Thursday morning?

Working in Service Fusion with Elaichi

  • List all Service Fusion availability
  • List all Service Fusion calendar tasks
  • Get single Service Fusion calendar task by ID
Ask anything…
Governance / Audit log Last 24 hours
Service Fusion Get single Service Fusion calendar task by ID Emily Carter · Claude · 9:41 AM Done
Service Fusion List all Service Fusion calendar tasks Emily Carter · Claude · 9:41 AM Done
Service Fusion List all Service Fusion availability Emily Carter · Claude · 9:41 AM Done
Service Fusion List all Service Fusion crews Megan Brooks · ChatGPT · 9:38 AM Done
Service Fusion Get single Service Fusion crew by ID Ryan Hayes · Cursor · 9:35 AM Done

How to connect Service Fusion to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Service Fusion MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

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

Service Fusion MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

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

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Service Fusion MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 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 Service Fusion to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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 Service Fusion through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Service Fusion is logged.

  • Dispatch

    Find an open crew for tomorrow morning

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

  • Office

    Set up the customer and job after a call

    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.

  • Sales

    Draft an estimate while the lead is warm

    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.

  • Finance

    Review outstanding invoices before month end

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

  • Field service

    Know the equipment before the truck rolls

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

  • Operations

    See where every job stands today

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

Try asking

  • “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”

See all 30 Service Fusion tools →

What connecting Service Fusion gets you

6 screens from Elaichi, each doing one job for your Service Fusion account.

Elaichi Agent

Ask Elaichi to work across your apps.

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

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask plain questions, get live job answers.

Three starter prompts read live Service Fusion jobs, crews and invoices and reply in plain language.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint, every client, no shared key.

Claude, ChatGPT and Cursor reach Service Fusion through one governed org endpoint, no SDK required.

ElaichiTools
Tool Action Description
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 < 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 < 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 < 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.

Tool catalog

30 Service Fusion tools, no code to write.

Customers, jobs, estimates, invoices, crews, equipment and calendar tasks, all cataloged and ready.

ElaichiToolboxes
Name Source template Tools Created

Dispatch toolbox

Service Fusion · crews and availability

Service Fusion starter 18 Mar 4, 2026

Office toolbox

Service Fusion · customers and jobs

— 9 Mar 2, 2026

Sales toolbox

Service Fusion · estimates and new customers

— 24 Feb 27, 2026

Finance toolbox

Service Fusion · invoices and payment types

Service Fusion starter 6 Feb 19, 2026

Field service toolbox

Service Fusion · customer equipment and job details

— 31 Jan 30, 2026

Operations toolbox

Service Fusion · job statuses and categories

— 12 Jan 22, 2026

Toolboxes

Every team gets its own toolbox.

Dispatch sees crews and availability, finance sees invoices, each scoped to the team that needs it.

ElaichiConnections
Connection Scope Status Access
SE

Service Fusion (Dispatch)

Connected by Emily Carter

Personal • Active 1 team · 6 members
SE

Service Fusion (Front office)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
SE

Service Fusion (Sales)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
SE

Service Fusion (Billing)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
SE

Service Fusion (Field techs)

Connected by Ryan Hayes

Personal • Active Not shared
SE

Service Fusion (Ops)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates work through it, never see the credential.

One person connects Service Fusion, shares it with teams, and nobody else handles the secret.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Service Fusion Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Service Fusion Customers Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Service Fusion Customers List Toolbox

Audit log

Know who created which job, and when.

Every Service Fusion call is logged with who, what, type and resource, append-only.

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.

Service Fusion digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch customers

    Service Fusion

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Service Fusion

    Queued

Workflows

A schedule starts the job digest itself.

Jobs are fetched, grouped by status, drafted into a digest, approved by you, then posted back.

Service Fusion health

Refreshed 4 minutes ago · every 15 minutes · from the customers collection

Live

Customers

1,284 ↓ 12%

Jobs

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Customers created

Last 14 days

By team

Share of activity

Dispatch 34%

Front office 27%

Sales 21%

Billing 18%

Collections and dashboards

Job numbers that refresh without being asked.

Four metrics, fourteen days of jobs created and a breakdown by team, computed with no model.

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Service Fusion, by what to check
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 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Service Fusion tools for your AI agents

30 tools are ready to call through Elaichi's MCP endpoint the moment you connect Service Fusion, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Questions, answered

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.

Put Service Fusion 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