Service Fusion MCP by usefulapi

Each tool targets a distinct resource + action (customer, job, estimate, invoice, tech, crew, calendar task, equipment) plus a clear set of reference-data lookups, so misselection is unlikely. The only mild overlap is list_jobs/list_estimates with expand parameters versus get_job/get_estimate, which return the same detail under different names.

Every tool follows the same servicefusion_verb_noun snake_case pattern with a small verb vocabulary (create, get, list). Singular/plural is used deliberately and correctly: get_* for one record, list_* for collections.

At 26 tools the surface is at the heavy edge for what is essentially a field-service CRUD domain, and roughly six of them are small reference-data lookups (categories, statuses, sources, payment types, departments). Each tool does earn a place, but the set could be consolidated through expand/filter parameters.

Read coverage is strong (list + get across customers, jobs, estimates, invoices, techs, crews, equipment, calendar tasks) and creates exist for customers, jobs and estimates. However, there is no update or delete/cancel operation anywhere, and no create for invoices, payments or calendar tasks, which are core lifecycle gaps for an agent trying to change records.