Service Fusion MCP by usefulapi

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

• 연결 방식: 클라우드에서 실행
• 전송 방식: Streamable HTTP
• 카테고리: 기타

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

필요한 것

• 클라우드에서 실행설치할 것 없음. 인터넷으로 연결돼요

어떤 앱을 쓰세요?

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

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

도구 이름과 설명은 서버가 2026년 11월 6일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.

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

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검

• ✓ 통과

  제작자와 저장소 일치

  레지스트리 이름이 도메인 usefulapi.io 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)

• … 아직 점검 안 함

  계속 관리되고 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• … 아직 점검 안 함

  라이선스 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• ✓ 통과

  엔드포인트 응답

  67ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✓ 통과

  도구 설명에 숨겨진 지시 없음

  도구 설명 26개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요

기타 카테고리의 다른 서버와 비교i

• 이 카테고리의 다른 서버 32599개 중 0%보다 스타가 많아요
• 이 카테고리의 다른 서버 32599개 중 99%보다 최근에 레지스트리에 공개됐어요
• 기본 점검 결과가 이 카테고리의 다른 서버 32599개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

제작자의 README

{