Synchroteam MCP by usefulapi

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

• Conexión: Se ejecuta en la nube
• Transporte: Streamable HTTP
• Categoría: Otros

Instalación

Elige la app de IA que usas y copia la configuración.

Necesitas

• Se ejecuta en la nubeNo hay nada que instalar; se conecta por internet

¿Qué app usas?

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

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Nombres y descripciones de las herramientas tal como los informó el servidor el 6 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.

• 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

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026

• ✓ Superada

  El creador coincide con el repo

  El nombre en el registro se verificó con el dominio usefulapi.io (el registro comprueba quién es dueño del dominio)

• … Aún sin revisar

  Sigue en mantenimiento

  Todavía no hemos leído este repo en GitHub

• … Aún sin revisar

  Tiene licencia

  Todavía no hemos leído este repo en GitHub

• ✓ Superada

  El endpoint responde

  Respondió en 19 ms (HTTP 200)

• – No aplica

  Inicio de sesión con OAuth

  No hace falta iniciar sesión

• ✓ Superada

  Sin instrucciones ocultas en las descripciones de herramientas

  Leímos 33 descripciones de herramientas y no encontramos instrucciones ocultas para la IA

Comparado con otros en Otrosi

• Más estrellas que el 0% de los otros 32410 servidores de esta categoría
• Publicado en el registro más recientemente que el 97% de los otros 32410 servidores de esta categoría
• Revisiones básicas iguales o mejores que el 100% de los otros 32410 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

README del creador

{