# Service Fusion MCP by usefulapi (remote · service-fusion.usefulapi.io)

Read Service Fusion customers, jobs, estimates, invoices and schedule; create customers and jobs.

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `service-fusion.usefulapi.io`: 61/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-service-fusion/service-fusion.md), [page](https://verifymcp.io/servers/io-usefulapi-service-fusion/service-fusion)

## Channel facts

- Endpoint: `https://service-fusion.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.4.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 74/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 5681 tokens (~218/item across 26 items; 26 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 26 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Service Fusion MCP by usefulapi server?

Service Fusion MCP by usefulapi is a hosted endpoint at https://service-fusion.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-usefulapi-service-fusion 'https://service-fusion.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-service-fusion": {
      "url": "https://service-fusion.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-service-fusion": {
      "type": "http",
      "url": "https://service-fusion.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-service-fusion]
url = "https://service-fusion.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-service-fusion": {
      "type": "remote",
      "url": "https://service-fusion.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-service-fusion --url 'https://service-fusion.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-service-fusion:
    url: "https://service-fusion.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-service-fusion": {
      "Transport": "http",
      "Url": "https://service-fusion.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-service-fusion -t streamable-http -u 'https://service-fusion.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-service-fusion": {
      "type": "http",
      "url": "https://service-fusion.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-25 (score 61, 0)

- [functional] Server version: 1.4.0 → 1.4.3

### 2026-10-24 (score 61, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.3.0 → 1.4.0
- [functional] Server version: 1.2.0 → 1.3.0
- [functional] Server version: 1.0.0 → 1.2.0

### 2026-10-23 (score 60)

First indexed and scored.

## MCP tools (26)

### `servicefusion_get_me` (~37 tokens)

Get current user

The Service Fusion user the API credentials belong to: id, name and email. Use it to check the connection. GET /me.

### `servicefusion_list_customers` (~343 tokens)

List customers

List customers (newest id order unless sorted). Filter by name, contact, address, city, postal code, phone, email, tags or last-serviced date. Add expand=contacts,locations,custom_fields to include them. GET /customers.

Input parameters:

- `address` (string): Street address (partial match).
- `city` (string): City (exact match).
- `contact_first_name` (string): Contact first name (partial match).
- `contact_last_name` (string): Contact last name (partial match).
- `email` (string): Email (exact match).
- `expand` (array): Extra data to include: contacts, contacts.phones, contacts.emails, locations, custom_fields.
- `fields` (string): Only return these fields, comma-separated (for example id,customer_name). Default: all.
- `last_serviced_from` (string): Last serviced on or after this date, yyyy-mm-dd.
- `last_serviced_to` (string): Last serviced on or before this date, yyyy-mm-dd.
- `name` (string): Customer name (partial match).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-50 (default 10).
- `phone` (string): Phone (partial match).
- `postal_code` (string): Postal/ZIP code (exact match).
- `sort` (string): Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).
- `tags` (string): Tags, comma-separated (exact match).

### `servicefusion_get_customer` (~97 tokens)

Get customer

One customer by id, optionally with contacts, phones, emails, locations and custom fields. GET /customers/{id}.

Input parameters:

- `customer_id` (integer, required): Service Fusion customer id.
- `expand` (array): Extra data to include: contacts, contacts.phones, contacts.emails, locations, custom_fields.
- `fields` (string): Only return these fields, comma-separated (for example id,customer_name). Default: all.

### `servicefusion_list_customer_equipment` (~166 tokens)

List customer equipment

List the equipment on file for a customer (type, make, model, serial number, warranty and install dates). GET /customers/{id}/equipment.

Input parameters:

- `customer_id` (integer, required): Service Fusion customer id.
- `expand` (array): Extra data to include: custom_fields.
- `fields` (string): Only return these fields, comma-separated (for example id,customer_name). Default: all.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-50 (default 10).
- `sort` (string): Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).

### `servicefusion_get_customer_equipment` (~101 tokens)

Get customer equipment

One piece of equipment of a customer. GET /customers/{customer_id}/equipment/{equipment_id}.

Input parameters:

- `customer_id` (integer, required): Service Fusion customer id.
- `equipment_id` (integer, required): Equipment id (from servicefusion_list_customer_equipment).
- `expand` (array): Extra data to include: custom_fields.
- `fields` (string): Only return these fields, comma-separated (for example id,customer_name). Default: all.

### `servicefusion_list_jobs` (~610 tokens)

List jobs

List jobs (work orders). Filter by status, number, PO or invoice number, customer, contact, address, phone, email, category, source and start/end/updated/closed dates. Add expand (techs_assigned, services, products, payments, invoices, visits, notes, ...) for detail. GET /jobs.

Input parameters:

- `address` (string): Street address (partial match).
- `category` (string): Job categories, comma-separated (exact match).
- `city` (string): City (exact match).
- `closed_from` (string): Closed at or after (RFC 3339 date-time with timezone).
- `closed_to` (string): Closed at or before (RFC 3339 date-time with timezone).
- `contact_first_name` (string): Contact first name (partial match).
- `contact_last_name` (string): Contact last name (partial match).
- `customer_name` (string): Customer name (partial match).
- `email` (string): Email (exact match).
- `end_date_from` (string): Job end date on or after, yyyy-mm-dd.
- `end_date_to` (string): Job end date on or before, yyyy-mm-dd.
- `expand` (array): Extra data to include: agents, custom_fields, pictures, documents, equipment, equipment.custom_fields, techs_assigned, tasks, notes, products, services, other_charges, labor_charges, expenses, paymen…
- `fields` (string): Only return these fields, comma-separated (for example id,customer_name). Default: all.
- `invoice_number` (string): Invoice number (partial match).
- `number` (string): Job number (partial match).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `parent_customer_name` (string): Parent customer name (partial match).
- `per_page` (integer): Results per page, 1-50 (default 10).
- `phone` (string): Phone (partial match).
- `po_number` (string): PO number (partial match).
- `sort` (string): Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).
- `source` (string): Sources, comma-separated (exact match).
- `start_date_from` (string): Job start date on or after, yyyy-mm-dd.
- `start_date_to` (string): Job start date on or before, yyyy-mm-dd.
- `status` (string): Job status names, comma-separated (exact match; see servicefusion_list_job_statuses).
- `updated_from` (string): Updated at or after (RFC 3339 date-time with timezone).
- `updated_to` (string): Updated at or before (RFC 3339 date-time with timezone).
- `zip_code` (string): Postal/ZIP code (exact match).

### `servicefusion_get_job` (~146 tokens)

Get job

One job by id, optionally with technicians, line items, labor, expenses, payments, invoices, notes, visits and more. GET /jobs/{id}.

Input parameters:

- `expand` (array): Extra data to include: agents, custom_fields, pictures, documents, equipment, equipment.custom_fields, techs_assigned, tasks, notes, products, services, other_charges, labor_charges, expenses, paymen…
- `fields` (string): Only return these fields, comma-separated (for example id,customer_name). Default: all.
- `job_id` (integer, required): Service Fusion job id.

### `servicefusion_list_estimates` (~501 tokens)

List estimates

List estimates (quotes). Filter by status, number, PO number, customer, contact, address, phone, email, category, source and start/end/requested dates. GET /estimates.

Input parameters:

- `address` (string): Street address (partial match).
- `category` (string): Categories, comma-separated (exact match).
- `city` (string): City (exact match).
- `contact_first_name` (string): Contact first name (partial match).
- `contact_last_name` (string): Contact last name (partial match).
- `customer_name` (string): Customer name (partial match).
- `email` (string): Email (exact match).
- `end_date_from` (string): End date on or after, yyyy-mm-dd.
- `end_date_to` (string): End date on or before, yyyy-mm-dd.
- `expand` (array): Extra data to include: agents, custom_fields, pictures, documents, equipment, equipment.custom_fields, techs_assigned, tasks, notes, products, services, other_charges, payments, signatures, printable…
- `fields` (string): Only return these fields, comma-separated (for example id,customer_name). Default: all.
- `number` (string): Estimate number (partial match).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `parent_customer_name` (string): Parent customer name (partial match).
- `per_page` (integer): Results per page, 1-50 (default 10).
- `phone` (string): Phone (partial match).
- `po_number` (string): PO number (partial match).
- `requested_from` (string): Requested at or after (RFC 3339 date-time with timezone).
- `requested_to` (string): Requested at or before (RFC 3339 date-time with timezone).
- `sort` (string): Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).
- `source` (string): Sources, comma-separated (exact match).
- `start_date_from` (string): Start date on or after, yyyy-mm-dd.
- `start_date_to` (string): Start date on or before, yyyy-mm-dd.
- `status` (string): Estimate status names, comma-separated (exact match).
- `zip_code` (string): Postal/ZIP code (exact match).

### `servicefusion_get_estimate` (~126 tokens)

Get estimate

One estimate by id, optionally with line items, technicians, notes, tags and more. GET /estimates/{id}.

Input parameters:

- `estimate_id` (integer, required): Service Fusion estimate id.
- `expand` (array): Extra data to include: agents, custom_fields, pictures, documents, equipment, equipment.custom_fields, techs_assigned, tasks, notes, products, services, other_charges, payments, signatures, printable…
- `fields` (string): Only return these fields, comma-separated (for example id,customer_name). Default: all.

### `servicefusion_list_invoices` (~146 tokens)

List invoices

List invoices with number, total, paid flag, dates and the customer. The API has no invoice filters: sort and page instead (for example sort=-date). GET /invoices.

Input parameters:

- `fields` (string): Only return these fields, comma-separated (for example id,customer_name). Default: all.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-50 (default 10).
- `sort` (string): Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).

### `servicefusion_get_invoice` (~59 tokens)

Get invoice

One invoice by id. GET /invoices/{id}.

Input parameters:

- `fields` (string): Only return these fields, comma-separated (for example id,customer_name). Default: all.
- `invoice_id` (integer, required): Service Fusion invoice id.

### `servicefusion_list_calendar_tasks` (~269 tokens)

List calendar tasks

List calendar tasks (appointments and to-dos on the schedule) for one day (start_date or end_date alone), a date range (both) and/or given users. A task is returned when it overlaps the range. GET /calendar-tasks.

Input parameters:

- `end_date` (string): Range end, yyyy-mm-dd. Give BOTH start_date and end_date for a range; with only one of them the API returns tasks on that single day.
- `expand` (array): Extra data to include: repeat.
- `fields` (string): Only return these fields, comma-separated (for example id,customer_name). Default: all.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-50 (default 10).
- `sort` (string): Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).
- `start_date` (string): Range start, yyyy-mm-dd. Give BOTH start_date and end_date for a range; with only one of them the API returns tasks on that single day.
- `user_ids` (array): Only tasks assigned to these user (technician) ids.

### `servicefusion_get_calendar_task` (~75 tokens)

Get calendar task

One calendar task by id. GET /calendar-tasks/{id}.

Input parameters:

- `calendar_task_id` (integer, required): Calendar task id.
- `expand` (array): Extra data to include: repeat.
- `fields` (string): Only return these fields, comma-separated (for example id,customer_name). Default: all.

### `servicefusion_get_availability` (~339 tokens)

Get technician availability

Open time slots for technicians and/or crews over up to 8 days (end_date at most 7 days after start_date). Filter by technician, crew, department, experience level and slot length. GET /availability.

Input parameters:

- `crew_ids` (array): Only these crew ids.
- `departments` (array): Technician departments (any may match).
- `end_date` (string, required): Last day (inclusive), yyyy-mm-dd; at most 7 days after start_date.
- `end_time` (string): Only slots ending at or before this time of day, HH:MM.
- `experience_levels` (array): Experience levels 0-10 (any may match).
- `ignore_work_schedule` (boolean): Ignore each technician's work schedule; only the time window limits the slots.
- `max_duration` (integer): Maximum slot length in minutes.
- `min_duration` (integer): Minimum slot length in minutes.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Slots per page, 1-100.
- `scope` (string): Individual technician slots, crew slots, or both (the API default is techs; pass all to include crews).
- `sort` (string): Sort by date and/or duration, e.g. date,-duration (API default: date).
- `start_date` (string, required): First day (inclusive), yyyy-mm-dd.
- `start_time` (string): Only slots starting at or after this time of day, HH:MM.
- `tech_ids` (array): Only these technician ids.

### `servicefusion_list_techs` (~212 tokens)

List technicians

List technicians and sales reps (name, contact details, department, title, color, field-worker and sales-rep flags). GET /techs.

Input parameters:

- `email` (string): Email (partial match).
- `fields` (string): Only return these fields, comma-separated (for example id,customer_name). Default: all.
- `first_name` (string): First name (partial match).
- `last_name` (string): Last name (partial match).
- `nickname_on_dispatch` (string): Nickname on the dispatch board (partial match).
- `nickname_on_workorder` (string): Nickname on work orders (partial match).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-50 (default 10).
- `sort` (string): Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).

### `servicefusion_get_tech` (~60 tokens)

Get technician

One technician by id. GET /techs/{id}.

Input parameters:

- `fields` (string): Only return these fields, comma-separated (for example id,customer_name). Default: all.
- `tech_id` (integer, required): Service Fusion technician id.

### `servicefusion_list_tech_departments` (~36 tokens)

List technician departments

The technician department names configured in the account (useful for availability filters). GET /techs/departments.

### `servicefusion_list_crews` (~140 tokens)

List crews

List crews (named groups of technicians), optionally with their members. GET /crews.

Input parameters:

- `expand` (array): Extra data to include: techs.
- `fields` (string): Only return these fields, comma-separated (for example id,customer_name). Default: all.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-50 (default 10).
- `sort` (string): Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).

### `servicefusion_get_crew` (~79 tokens)

Get crew

One crew by id, optionally with its technicians. GET /crews/{id}.

Input parameters:

- `crew_id` (integer, required): Service Fusion crew id.
- `expand` (array): Extra data to include: techs.
- `fields` (string): Only return these fields, comma-separated (for example id,customer_name). Default: all.

### `servicefusion_list_job_categories` (~126 tokens)

List job categories

The job category names to use when creating or filtering jobs. GET /job-categories.

Input parameters:

- `fields` (string): Only return these fields, comma-separated (for example id,customer_name). Default: all.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-50 (default 10).
- `sort` (string): Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).

### `servicefusion_list_job_statuses` (~137 tokens)

List job statuses

The job status names (code, name, custom flag, category) to use when creating or filtering jobs. GET /job-statuses.

Input parameters:

- `fields` (string): Only return these fields, comma-separated (for example id,customer_name). Default: all.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-50 (default 10).
- `sort` (string): Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).

### `servicefusion_list_payment_types` (~121 tokens)

List payment types

The payment types configured in the account. GET /payment-types.

Input parameters:

- `fields` (string): Only return these fields, comma-separated (for example id,customer_name). Default: all.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-50 (default 10).
- `sort` (string): Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).

### `servicefusion_list_sources` (~132 tokens)

List lead sources

The lead/referral sources (short and long names) to use when creating or filtering jobs and estimates. GET /sources.

Input parameters:

- `fields` (string): Only return these fields, comma-separated (for example id,customer_name). Default: all.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-50 (default 10).
- `sort` (string): Sort fields, comma-separated; a leading - sorts descending (for example -updated_at,customer_name).

### `servicefusion_create_customer` (~296 tokens)

Create customer

WRITE: create a customer in Service Fusion, optionally with contacts (phones, emails) and service locations. It is visible to the whole team and cannot be deleted through this API; creating the same name twice makes two customers, so search with servicefusion_list_customers first. POST /customers.

Input parameters:

- `account_number` (string)
- `agent` (string): Sales agent name.
- `assigned_contract` (string)
- `contacts` (array)
- `credit_rating` (string)
- `custom_fields` (array): Custom fields: [{name, value}] with names as configured in Service Fusion.
- `customer_name` (string, required): Customer (company or person) name.
- `discount` (number)
- `discount_type` (string)
- `industry` (string)
- `is_bill_for_drive_time` (boolean)
- `is_taxable` (boolean)
- `is_vip` (boolean)
- `labor_charge_default_rate` (number)
- `labor_charge_type` (string)
- `locations` (array)
- `parent_customer` (string): Name of an existing parent customer.
- `payment_terms` (string)
- `payment_type` (string)
- `private_notes` (string): Internal notes.
- `public_notes` (string): Notes shown on customer-facing documents.
- `referral_source` (string)
- `tax_item_name` (string)

### `servicefusion_create_job` (~559 tokens)

Create job

WRITE: create a job (work order) for a customer, optionally with address, category, source, assigned technicians, tasks, notes, products, services and other charges. It appears on the team's schedule and cannot be deleted through this API; creating twice makes two jobs. Look up category, source and status names with the list tools first. POST /jobs.

Input parameters:

- `called_in_by` (string)
- `category` (string): Job category name (see servicefusion_list_job_categories).
- `check_number` (string)
- `city` (string)
- `completion_notes` (string)
- `contact_first_name` (string)
- `contact_last_name` (string)
- `contract` (string)
- `custom_fields` (array): Custom fields: [{name, value}] with names as configured in Service Fusion.
- `customer_name` (string, required): Customer name exactly as in Service Fusion (see servicefusion_list_customers); an unknown name is created as a new customer.
- `customer_payment_terms` (string)
- `description` (string): Job/estimate description (max 500 characters).
- `duration` (integer): Duration in seconds, 0-86400 (3600 = 1 hour).
- `end_date` (string): End date, yyyy-mm-dd.
- `gate_instructions` (string)
- `is_gated` (boolean)
- `is_requires_follow_up` (boolean)
- `location_name` (string)
- `note_to_customer` (string)
- `notes` (array): Internal notes: [{notes}].
- `other_charges` (array)
- `payment_type` (string)
- `phase` (string)
- `po_number` (string)
- `postal_code` (string)
- `priority` (string)
- `products` (array)
- `project` (string)
- `services` (array)
- `source` (string): Lead source name (see servicefusion_list_sources).
- `start_date` (string): Start date, yyyy-mm-dd.
- `state_prov` (string)
- `status` (string): Status name (see servicefusion_list_job_statuses).
- `street_1` (string)
- `street_2` (string)
- `tasks` (array)
- `tech_notes` (string): Notes for the technician.
- `techs_assigned` (array): Technicians to assign: [{id}] or [{first_name, last_name}].
- `time_frame_promised_end` (string): Promised arrival window end, HH:MM.
- `time_frame_promised_start` (string): Promised arrival window start, HH:MM.

### `servicefusion_create_estimate` (~508 tokens)

Create estimate

WRITE: create an estimate (quote) for a customer, optionally with address, category, source, technicians, tasks, notes, products, services, other charges and tags. It cannot be deleted through this API; creating twice makes two estimates. POST /estimates.

Input parameters:

- `category` (string): Job category name (see servicefusion_list_job_categories).
- `city` (string)
- `contact_first_name` (string)
- `contact_last_name` (string)
- `contract` (string)
- `custom_fields` (array): Custom fields: [{name, value}] with names as configured in Service Fusion.
- `customer_name` (string, required): Customer name exactly as in Service Fusion (see servicefusion_list_customers); an unknown name is created as a new customer.
- `description` (string): Job/estimate description (max 500 characters).
- `duration` (integer): Duration in seconds, 0-86400 (3600 = 1 hour).
- `gate_instructions` (string)
- `is_gated` (boolean)
- `location_name` (string)
- `note_to_customer` (string)
- `notes` (array): Internal notes: [{notes}].
- `opportunity_owner` (string): Name of the opportunity owner.
- `opportunity_rating` (integer): Opportunity rating, 0-5.
- `other_charges` (array)
- `phase` (string)
- `po_number` (string)
- `postal_code` (string)
- `products` (array)
- `project` (string)
- `services` (array)
- `source` (string): Lead source name (see servicefusion_list_sources).
- `start_date` (string): Start date, yyyy-mm-dd.
- `state_prov` (string)
- `status` (string): Status name (see servicefusion_list_job_statuses).
- `street_1` (string)
- `street_2` (string)
- `tags` (array): Tags: [{tag}].
- `tasks` (array)
- `tech_notes` (string): Notes for the technician.
- `techs_assigned` (array): Technicians to assign: [{id}] or [{first_name, last_name}].
- `time_frame_promised_end` (string): Promised arrival window end, HH:MM.
- `time_frame_promised_start` (string): Promised arrival window start, HH:MM.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-service-fusion/service-fusion#diagnostics

## Score history

- 2026-10-25: 61
- 2026-10-24: 61
- 2026-10-23: 60

## Common questions

### What is the Service Fusion MCP by usefulapi server?

Service Fusion MCP by usefulapi is listed in the public MCP registry as io.usefulapi/service-fusion. Read Service Fusion customers, jobs, estimates, invoices and schedule; create customers and jobs. This page covers its hosted endpoint (https://service-fusion.usefulapi.io/mcp).

### Is the Service Fusion MCP by usefulapi server safe to use?

Service Fusion MCP by usefulapi scores 61 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Service Fusion MCP by usefulapi server expose?

Service Fusion MCP by usefulapi exposes 26 tools: servicefusion_get_me, servicefusion_list_customers, servicefusion_get_customer, servicefusion_list_customer_equipment, servicefusion_get_customer_equipment, and 21 more. Their descriptions and schemas cost roughly 5,421 tokens of context every time the server is loaded.

### Does the Service Fusion MCP by usefulapi server require authentication?

Yes. Service Fusion MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Service Fusion MCP by usefulapi server still maintained?

Service Fusion MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://service-fusion.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/service-fusion/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-service-fusion/service-fusion.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-service-fusion/service-fusion.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-service-fusion/service-fusion