Service Fusion MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Other

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://service-fusion.usefulapi.io/mcp

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

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

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

https://service-fusion.usefulapi.io/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.

• servicefusion_get_me

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

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

• servicefusion_get_customer

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

• servicefusion_list_customer_equipment

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

• servicefusion_get_customer_equipment

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

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

• servicefusion_get_job

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

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

• servicefusion_get_estimate

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

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

• servicefusion_get_invoice

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

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

• servicefusion_get_calendar_task

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

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

• servicefusion_list_techs

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

• servicefusion_get_tech

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

• servicefusion_list_tech_departments

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

• servicefusion_list_crews

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

• servicefusion_get_crew

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

• servicefusion_list_job_categories

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

• servicefusion_list_job_statuses

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

• servicefusion_list_payment_types

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

• servicefusion_list_sources

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

• servicefusion_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

• servicefusion_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 c

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

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 31 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 26 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

• More stars than 0% of the other 32708 servers in this category
• Published to the registry more recently than 98% of the other 32708 servers in this category
• Basic checks equal to or better than 100% of the other 32708 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{