The Syncro PSA, scriptable.
A typed TypeScript client, a command-line interface, and an MCP server for the Syncro MSP REST API. Drive tickets, customers, assets, invoices, and RMM alerts from a shell or from any AI agent that speaks MCP.
How do you drive the Syncro PSA from a shell or an agent?
The Syncro UI is the workflow until it slows you down. Then you want the workflow programmable. The SDK gives you that, three ways.
SDK
Typed TypeScript client.
Auto-paginated, rate-limited, typed responses for every endpoint. Drop it into a Node or Bun project, set credentials, and call the API like a library instead of a swagger document.
CLI
Daily ops without the browser.
Configure once. List tickets, search customers, manage RMM alerts, send invoices, and assign assets straight from a terminal. Output as table, JSON, or plain text for pipelines.
MCP
Syncro inside any agent.
Run the MCP server and Claude, Cursor, or your own agent can drive Syncro the same way the CLI does. Tickets, customers, alerts, all accessible by tool call.
The Syncro surface area.
Coverage tracks our daily MSP operations. If we touch it in the Syncro UI, we want to script it.
Tickets
List, get, comment, timers, line items
Customers
List, get, search, create, update
Contacts
List, get, create, update
Assets
List, get, patches
Invoices
List, get, email
Estimates
List, get, create, update, convert
Leads
List, get, create, update
RMM Alerts
List, get, clear, mute
Wiki
List, get, create, update, delete
What it looks like in a shell.
Configure once
syncro config \ --subdomain your-subdomain \ --api-key your-api-key syncro customers list
Pipe to anything
syncro tickets list \
--status open \
--format json \
| jq '.[] | {id, subject}'Every command takes --format table|json|plain. Table is for reading. JSON is for piping. Plain is for scripts that want one value per line.
Internal tooling, made public.
Hexaxia Technologies runs on Syncro. The SDK is what our operators use every day to keep the workflow fast, the alerts triaged, and the tickets moving. We wrote it for ourselves first.
Other MSPs and the AI agents that work inside them tend to need the same primitives. Coverage. Auth. Rate limiting. Typed responses. A CLI for the operator. An MCP surface for the agent. So we packaged the internal tools and made them available.
Script your Syncro.
The SDK is in active development. We are working with a small number of MSPs to round out coverage where they need it. Tell us what you would drive first.