# Service Fusion Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Service Fusion

Manage service jobs, estimates, customers and technician schedules for field service businesses.

- Record: https://musedirectory.ai/connector/service-fusion
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/service-fusion/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 265ms, checked 2026-10-29T21:11:29Z
- Endpoint: https://service-fusion.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T21:11:29Z)
- Source: Found in the official MCP Registry (io.usefulapi/service-fusion) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fservice-fusion

Connects to Service Fusion field service software. Muse can read and create customers, jobs and estimates; view invoices, equipment and technician availability; and check the schedule and calendar tasks.

Example request: "Show me all open jobs for today and which technicians are available to assign to a new service call."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Service Fusion to help me. It is a free service with an MCP server at https://service-fusion.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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.

Screening checks:
- MCP handshake: pass (Answered in 265ms)
- Domain against threat feeds (Cloudflare security DNS): pass (service-fusion.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (26 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)