Read Synchroteam jobs, customers, sites, equipment and parts; create, schedule and complete jobs. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"synchroteam": {
"url": "https://synchroteam.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"synchroteam": {
"type": "http",
"url": "https://synchroteam.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Synchroteam domain and Synchroteam API key.
The domain is the first part of your Synchroteam address (mycompany for mycompany.synchroteam.com). Find the key in Synchroteam under Configuration → Authentication Key. The key is account-wide and acts with administrator rights. It is used only to call the Synchroteam API on your behalf and is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Synchroteam domain and Synchroteam API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
synchroteam_list_customers | read | 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 | read | 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 | read | List sites List or search sites (a customer's locations): by name, customer, active flag, change time. GET /site/list. |
synchroteam_get_site | read | Get site One site by id, myId or exact name: address, contact, customer, custom fields, tags. GET /site/details. |
synchroteam_list_equipment | read | List equipment List or search pieces of equipment (assets) by name, customer, site, active flag, change time. GET /equipment/list. |
synchroteam_get_equipment | read | Get equipment One piece of equipment by id, myId or exact name, with its customer and site. GET /equipment/details. |
synchroteam_list_jobs | read | 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 | read | 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 | read | 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 | read | 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 | read | List users (technicians and staff) List users: login, name, profile (technician, manager, administrator), teams, skills, last known location. Passwords are never returned. GET /user/list. |
synchroteam_get_user | read | Get user One user by login or id. GET /user/details. |
synchroteam_list_teams | read | List teams List teams with member counts and tags. GET /team/list. |
synchroteam_list_parts | read | List parts and services List the parts and services catalog (reference, name, price, category, tax, tracked/serialized flags, type). GET /part/list. |
synchroteam_get_part | read | Get part One part or service by id or reference. GET /part/details. |
synchroteam_list_depots | read | List stock 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 | read | Get depot stock One stock depot by id, with the quantity of each part it holds. GET /depot/details. |
synchroteam_list_part_requests | read | List part requests List technicians' part requests (urgent, sent, completed, deleted flags). GET /partrequest/list. |
synchroteam_list_invoices | read | 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 | read | Get invoice One invoice by id, reference or number, with its lines. GET /invoice/details. |
synchroteam_list_quotations | read | List quotations List quotations (read only): number, status, customer, job, lines, totals. GET /quotation/list. |
synchroteam_get_quotation | read | Get quotation One quotation by id, reference or number, with its lines. GET /quotation/details. |
synchroteam_list_contracts | read | List contracts List service contracts by name, customer, site, period or active flag. GET /contract/list. |
synchroteam_list_projects | read | List projects List projects (groups of jobs) by customer, site, equipment or project type. GET /project/list. |
synchroteam_list_activities | read | List technician 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 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 | 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 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 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 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 error is returned. Synchroteam may send the account's 'job created' notifications (email/SMS/webhook, possibly to the customer), as configured. POST /job/send. |
synchroteam_schedule_job | write | 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 job by exactly one of id, my_id or num. POST /job/schedule. |
synchroteam_start_job | write | 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). Identify the job by exactly one of id, my_id or num. POST /job/start. |
synchroteam_complete_job | write | 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, technicians or the customer), as configured in Synchroteam. Identify the job by exactly one of id, my_id or num. POST /job/complete. |
synchroteam_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
synchroteam_request_feature | Request a missing feature Tell usefulapi that the user needs something the Synchroteam tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
synchroteam_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Synchroteam tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
synchroteam_cancel_subscription | Cancel the Pro subscription Cancel the caller's Synchroteam Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run synchroteam_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper account | $9/mo · $90/yr | Unlimited |
Pro covers this Synchroteam server only. Subscribe with synchroteam_upgrade (it returns a Stripe Checkout link). Cancel any time with synchroteam_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running synchroteam_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Synchroteam. The server calls the Synchroteam API with your own Synchroteam access, so it sees only the data that your account can see.
The login page asks for your Synchroteam domain and Synchroteam API key. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Synchroteam domain and Synchroteam API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Synchroteam API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Synchroteam.
Yes, if you approve it. 8 of the 33 Synchroteam tools can create or change data. The other 25 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Synchroteam server only. Run synchroteam_usage_status to see how many calls you used.
Ask the AI to run synchroteam_upgrade: it returns a Stripe Checkout link. To cancel, run synchroteam_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with synchroteam_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.