Synchroteam MCP server

What the model can do

Synchroteam field service management: jobs by status, date, technician, customer or site with schedule, actual times, parts and time entries; customers, sites, technicians, timeline notes, tasks and invoices; when you ask, can create, edit, schedule, start, pause, complete, validate, cancel or delete jobs, add or edit customers and sites, add timeline notes and tasks, and message technicians.

Reads

• synchroteam_list_jobsSynchroteam jobs: number, status, priority, customer, site, technician, scheduled and actual times, short description.
• synchroteam_get_jobOne Synchroteam job in full: description, status, customer, site, equipment, type, technicians, schedule and actual times, time entries, parts used…
• synchroteam_list_customersSynchroteam customers: id, your reference, name, city, tags, last change.
• synchroteam_list_sitesSynchroteam sites (a customer's locations): id, reference, name, customer, city, tags.
• synchroteam_list_usersSynchroteam users (technicians, managers, administrators): id, name, login, profile, teams and skilled trades.
• synchroteam_list_timelineThe timeline of a Synchroteam customer, site, equipment or job: notes, calls, emails and meetings logged by staff, and status notifications.
• synchroteam_list_tasksTasks (follow-ups, reminders, meetings) on a Synchroteam customer, site, equipment or job: content, due date, done date, assignee, category.
• synchroteam_list_invoicesSynchroteam invoices: number, reference, status (draft, new, sent, late, paid, cancelled), customer, job, subtotal, tax and total, payment date.

Acts, when you ask

These change something in Synchroteam. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• synchroteam_create_jobCreates a Synchroteam job for a customer, with status "created" (not yet scheduled, so no technician is notified).
• synchroteam_update_jobChanges a Synchroteam job's description, priority or type; only the fields given change.
• synchroteam_schedule_jobSchedules (or re-schedules) a Synchroteam job for a technician between two times; the job then appears on that technician's mobile app.
• synchroteam_change_job_statusMoves a Synchroteam job on: start (records it as started, by default now; any other job the technician has started is paused), pause, confirm…
• synchroteam_complete_jobMarks a Synchroteam job completed with its actual start and end times (account local time).
• synchroteam_validate_jobValidates a completed Synchroteam job (the manager's sign-off), recorded against the user given.
• synchroteam_cancel_jobCancels a Synchroteam job; it leaves the technician's schedule.
• synchroteam_delete_jobDeletes a Synchroteam job, permanently as far as the API goes (it offers no undelete for jobs).
• synchroteam_save_customerAdds a Synchroteam customer (name plus an address or a city), or with customer_id changes one; only the fields given change.
• synchroteam_set_customer_activeActivates or deactivates a Synchroteam customer by id (a deactivated customer is hidden from lists and new jobs).
• synchroteam_delete_customerDeletes a Synchroteam customer by id.
• synchroteam_save_siteAdds a site to a Synchroteam customer (name, an address or city, and the customer), or with site_id changes one; only the fields given change.
• synchroteam_add_timeline_noteAdds an item (a note, or a logged call, email or meeting) to the timeline of one Synchroteam customer, site, equipment or job.
• synchroteam_create_taskCreates a Synchroteam task (a follow-up, reminder or meeting) for a user, due on a date, on one customer, site, equipment or job.
• synchroteam_send_messageSends a message to the named technicians, delivered in their Synchroteam mobile app (staff only, not customers).

Connect it

First connect Synchroteam on Dashboard → Connections, then add Memtro to your client once. The Synchroteam tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Synchroteam connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which jobs are scheduled for tomorrow and who has them?
• › What parts were used on job 1187?
• › Which invoices are late?
• › Which jobs did Tom Reilly complete last week?
• › Send the north team's technicians a message that the depot closes early today.

Questions

Is this an official Synchroteam MCP server?

No. It is Memtro's MCP server with Memtro's Synchroteam connector behind it: the connector reads Synchroteam through its API with the credentials you connect on Dashboard → Connections, and Synchroteam publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Synchroteam?

Only when you ask, and only what it has been granted: create a job for a customer; edit a job's description, priority or type; schedule a job for a technician; start, pause, confirm or unschedule a job; complete a job with its actual times; validate a completed job; cancel a job; delete a job (permanent); add or edit a customer; activate or deactivate a customer; delete a customer; add or edit a site; add a note to a customer's, site's, equipment's or job's timeline; create a task on a customer, site, equipment or job; send a message to technicians' mobile app. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Work management

• Clio Manage MCP server
• Linear MCP server
• Jira MCP server
• Asana MCP server
• monday.com MCP server
• Airtable MCP server