Connect Syncro to Conduit

This walkthrough connects Syncro to Conduit through Syncro’s official hosted MCP server. One connection covers PSA and RMM. The default is to sign in with your Syncro account. An API key is only for a headless or service account that cannot open a browser.

If this organization already connected Syncro through Syncro (API connector), that connection keeps working. You do not reconnect it, and connecting the official server does not disconnect it.

Menu labels can change

Syncro changes its own screens. For the official server, follow Connect Syncro MCP. For an API token, follow Syncro’s API tokens guide.

Before you start

You need:

• A Conduit role that can manage connections — owner or admin on your organization.
• A Syncro account you can sign in with, for the default path.
• For the headless path only: permission to create an API token, and your Syncro subdomain — the first label of the address you sign in at (https://<subdomain>.syncromsp.com).

Step 1 — Sign in from Conduit

1. In Conduit, go to Connections (/org/catalog). Expected: the vendor catalog.
2. Find Syncro (under RMM) and click Connect. Expected: a page whose primary action is Sign in with Syncro. The API key is not on this page until you open Headless / service account.
3. Click Sign in with Syncro. Expected: Syncro’s own sign-in and consent screen.
4. Approve access. Expected: you land back in Conduit with Connected.

The connection is stored at the organization scope, so every technician in your org shares it. An account that does not belong to an organization connects at personal scope instead — see Vendor connections.

Headless / service account

Use this when the caller cannot open a browser — a service account or other automation. It is not the path for an interactive sign-in.

1. On the same connect page, open Headless / service account.
2. Create an API token in Syncro following Syncro’s guide, and copy the key.
3. Fill the fields:
   • API Key (required).
   • Subdomain (required) — just the first label, such as yourcompany for yourcompany.syncromsp.com, not a full URL. Syncro’s official server rejects a request that omits the subdomain.
4. Click Connect with API key. Expected: Conduit checks the key against Syncro’s official MCP server and shows Connected. A bad key or subdomain is rejected here.

Caution

Copy the key once and paste it into Conduit. Don’t paste it into chat, email, or a shared document. Conduit encrypts it at rest. If the key is exposed, revoke it in Syncro and create a new one.

Saving an API key here replaces the credential on this official connection only. It does not change a separate Syncro (API connector) connection, and it does not ask you to reconnect that one.

Already using Syncro (API connector)?

Organizations connected through the older API-key connector stay connected. No reconnect is required, and nothing on that connection changes when you open this page.

Open Syncro (API connector) in the catalog only to rotate the API key on a connection that is already there. New connections should use Syncro on this page. Connecting the official server does not disconnect the API connector. Both can be connected at the same time; they are separate credentials and separate tool names.

Verify it worked

Connect an MCP client to Conduit — Claude Desktop, Claude Code, Cursor, or any MCP-compatible client (see Connecting an AI client) — and ask it to run a read-only Syncro tool, such as listing customers or recent tickets. You should get real data back, and the call appears in your audit log with the correct user, vendor (syncro-official for this connection, or syncro for the API connector), and a successful status.

Writes still go through Conduit’s normal tool permissions. A member who is not allowed to write cannot send those calls just because the official server accepted the connection.

Troubleshooting

Symptom	Likely cause
The connect page asks for an OAuth client id instead of sending you to Syncro	Your Conduit operator has not finished registering the shared Syncro client yet. You can still use Headless / service account, or contact your operator or support.
You denied consent (or closed Syncro’s screen)	No connection is created. Click Sign in with Syncro again when you are ready to approve.
Headless connect fails with “Invalid Syncro subdomain.”	The subdomain must be a single DNS label — letters, digits, and hyphens only. Enter yourcompany, not a full URL.
Headless connect fails with “Invalid Syncro API key or subdomain.”	The key is wrong or revoked, or the subdomain does not match the account that created the key.
Headless connect fails with “Syncro MCP returned HTTP <status>.”	Syncro returned an unexpected error. Retry, and check the subdomain.
Tool calls return 403 “no credentials for vendor”	This Syncro connection is not stored at a scope this user can use. Connect it at the organization scope, or confirm the user’s team has a key.
An existing API-connector connection stopped appearing	It should not. That connection is a different catalog entry, Syncro (API connector), and connecting the official server does not remove it. If it is missing, the credential was disconnected separately — reconnecting it is a new action, not something this page requires.
Need to rotate a headless key	Create a new API token in Syncro, open Headless / service account, and save it again.

Related

• OAuth vendors — the consent flow Syncro’s sign-in uses, and why Syncro’s page does not redirect on its own.
• Vendor connections — credential scopes, rotation, and the full vendor catalog.
• Security — how Conduit encrypts and resolves the credential you just stored.
• Syncro MCP tools — the official tool list.