MarketplaceServicio de campo

Conectores de Servicio de campo

4 conectores de Servicio de campo listos para usar — 193 herramientas MCP en total: MFR Mobile Field Report, ServiceTitan, ServiceM8. Pega tus credenciales y tu agente podrá llamarlos. Sin servidor MCP que escribir.

// buscar en el catálogo
⌘K
4conectores
193herramientas MCP totales
0Sin credenciales
4
Filtrar
MFR Mobile Field Report
Servicio de campo

Manage field service operations with Mobile Field Report (MFR). Access service requests, appointments, companies, contacts, technicians, service objects, products, documents, time tracking, invoices, checklists, items, tags, qualifications, cost centers, and reports via OData API.

71herramientas
Jobber
Servicio de campo

Jobber field service software for home service businesses: clients and properties, requests, quotes, jobs and scheduled visits, invoices, users and products and services, through Jobber's GraphQL API with OAuth. Can create clients, jobs, quotes and invoices; it cannot email or approve quotes and invoices.

29herramientas
ServiceM8
Servicio de campo

ServiceM8 job management for trades and field service: jobs and statuses, clients and contacts, the schedule (job activities and allocations), staff, price list materials, job line items and payments, notes, attachment metadata and form responses. Can create and update jobs and clients, book and move staff, add line items, record payments and add notes.

36herramientas
ServiceTitan
Servicio de campo

ServiceTitan field service management for HVAC, plumbing, electrical and other trades: customers and locations, leads, jobs and appointments, dispatch, capacity and technician shifts, technicians and business units, invoices and payments, estimates, pricebook services and materials, memberships and phone calls. Can create customers, book jobs, add appointments, reschedule, assign technicians, add notes and cancel jobs.

57herramientas

Explorar por categoría

Los 4 conectores, de la A a la Z
Contribuir/~30 min

¿Falta un conector? Agrégalo en un JSON.

Cada adaptador es un único JSON en packages/backend/src/adapters/. Copia uno existente, cambia endpoint y auth, abre un PR — validado por tests parametrizados en build.

// adapters/de/my-adapter.json
{
  "slug": "my-erp",
  "name": "My ERP",
  "category": "erp",
  "authType": "BEARER_TOKEN",
  "tools": [/* ... */]
}