Synchroteam MCP by usefulapi

할 수 있는 일

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

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

설치

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

필요한 것

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

어떤 앱을 쓰세요?

https://synchroteam.usefulapi.io/mcp

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

{
  "mcpServers": {
    "synchroteam": {
      "url": "https://synchroteam.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "synchroteam": {
      "type": "http",
      "url": "https://synchroteam.usefulapi.io/mcp"
    }
  }
}

https://synchroteam.usefulapi.io/mcp

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

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

할 수 있는 일

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

• synchroteam_list_customers

  List or search customers (name wildcard, e-mail, active flag, change time). Returns name, address, contact, custom fields, tags. GET /customer/list.

• synchroteam_get_customer

  One customer by id, myId, exact name or e-mail, with address, contact, custom fields and tags. GET /customer/details.

• synchroteam_list_sites

  List or search sites (a customer's locations): by name, customer, active flag, change time. GET /site/list.

• synchroteam_get_site

  One site by id, myId or exact name: address, contact, customer, custom fields, tags. GET /site/details.

• synchroteam_list_equipment

  List or search pieces of equipment (assets) by name, customer, site, active flag, change time. GET /equipment/list.

• synchroteam_get_equipment

  One piece of equipment by id, myId or exact name, with its customer and site. GET /equipment/details.

• synchroteam_list_jobs

  List jobs (simplified: no report, parts or time entries) filtered by status, schedule window, technician, team, customer, site, equipment, job type or project. Use synchroteam_get_job for the full record. GET /job/list.

• synchroteam_get_job

  One job by num (the job number shown in the app), id or myId: status, customer/site/equipment, technician(s), schedule, actual times, time entries, parts used, report and custom fields. GET /job/details.

• synchroteam_get_job_photos

  Photo links of a job (url, file name, comment, report iteration). Image bytes are never returned. GET /job/photos.

• synchroteam_list_job_types

  List job types (name, default duration, priority, skills, default report). Use their id or name when creating a job. GET /jobtype/list.

• synchroteam_list_users

  List users: login, name, profile (technician, manager, administrator), teams, skills, last known location. Passwords are never returned. GET /user/list.

• synchroteam_get_user

  One user by login or id. GET /user/details.

• synchroteam_list_teams

  List teams with member counts and tags. GET /team/list.

• synchroteam_list_parts

  List the parts and services catalog (reference, name, price, category, tax, tracked/serialized flags, type). GET /part/list.

• synchroteam_get_part

  One part or service by id or reference. GET /part/details.

• synchroteam_list_depots

  List stock depots (warehouses and technician vans). The part quantities of one depot come from synchroteam_get_depot. GET /depot/list.

• synchroteam_get_depot

  One stock depot by id, with the quantity of each part it holds. GET /depot/details.

• synchroteam_list_part_requests

  List technicians' part requests (urgent, sent, completed, deleted flags). GET /partrequest/list.

• synchroteam_list_invoices

  List invoices (read only): number, status, customer, job, lines, totals. Filter by status, customer, site, job or time. GET /invoice/list.

• synchroteam_get_invoice

  One invoice by id, reference or number, with its lines. GET /invoice/details.

• synchroteam_list_quotations

  List quotations (read only): number, status, customer, job, lines, totals. GET /quotation/list.

• synchroteam_get_quotation

  One quotation by id, reference or number, with its lines. GET /quotation/details.

• synchroteam_list_contracts

  List service contracts by name, customer, site, period or active flag. GET /contract/list.

• synchroteam_list_projects

  List projects (groups of jobs) by customer, site, equipment or project type. GET /project/list.

• synchroteam_list_activities

  List time entries and unavailabilities (travel, at work, clock, unavailable) of technicians. start_date and end_date go together and return anything overlapping that range. GET /activity/list.

• synchroteam_create_customer

  WRITE: create a new customer (name and an address are required). If you pass myId and a customer with that myId already exists, nothing is created and an error is returned (use synchroteam_update_customer). POST /customer/send.

• synchroteam_update_customer

  WRITE: change fields of an existing customer by its numeric id. Only the fields you pass are changed; nothing is cleared. The customer id must exist (an unknown id fails). POST /customer/send.

• synchroteam_create_site

  WRITE: create a new site (a location of a customer). Needs a name, an address and the customer (id or myId). If myId already exists nothing is created and an error is returned. POST /site/send.

• synchroteam_create_equipment

  WRITE: create a new piece of equipment under a site or a customer (give exactly one of site or customer; both is refused). If myId already exists nothing is created and an error is returned. POST /equipment/send.

• synchroteam_create_job

  WRITE: create a new job for a customer (status created, not yet scheduled; use synchroteam_schedule_job to assign a technician and time). The customer is required (id, myId or exact name); site, equipment and job type are optional. If myId already exists nothing is created and an

• synchroteam_schedule_job

  WRITE: schedule a job for a technician between two times (also re-schedules a scheduled or paused job). Synchroteam may notify technicians and/or customers (email/SMS/webhook) as configured in the account's notification settings (SMS uses the account's paid credits). Identify the

• synchroteam_start_job

  WRITE: mark a job as started (status started, actual start now). If the job's technician already has another started job, Synchroteam pauses that one. Starting may trigger the account's 'job started' notifications (email/SMS/webhook to managers, technicians or the customer). Iden

• synchroteam_complete_job

  WRITE: mark a job as completed, optionally with the real start and end times (give actual_start and actual_end together: Synchroteam may refuse the call with only one of them). Completing may trigger the account's 'job completed' notifications (email/SMS/webhook to managers, tech

기본 점검i

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

• ✓ 통과

  제작자와 저장소 일치

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

• … 아직 점검 안 함

  계속 관리되고 있음

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

• … 아직 점검 안 함

  라이선스 있음

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

• ✓ 통과

  엔드포인트 응답

  9ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✓ 통과

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

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

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

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

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

대안

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

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

제작자의 README

{