Service Fusion MCP by usefulapi

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

Takes no parameters.

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.

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

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

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

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.

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

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

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

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.

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

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.

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

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.

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

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

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

Takes no parameters.

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

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

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

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

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

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

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.

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.

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.