Syncro Claude Plugins
Table of Contents
The Syncro Plugins repository in GitLab is the central hub for AI tools designed to enhance your workflow across Claude Chat, Cowork, and Code. Every plugin in this repository functions by combining a secure data bridge (Model Context Protocol/MCP Server) for live access to your Syncro data with built-in knowledge and skills to guide Claude's behavior.
The repository currently includes the Syncro Service Desk plugin, which transforms Claude into a specialized service desk assistant. It connects to your live Tickets, Invoices, Organizations, Assets, and Alerts, using Syncro conventions to ensure Claude executes common jobs and manages workflows consistently every single session.
Install the Plugin
Prerequisites
Before installing the Syncro Claude Plugin:
- Connect the Syncro MCP server. The Syncro Service Desk plugin declares the connector so you are prompted to authorize it on install, but it ships no credentials: you authenticate against your own Syncro Tenant, and the skills use whatever access that grants.
- On Claude Code, use claude --version to verify the version as 2.1.196 or later. (Earlier versions reject the install command with a misleading "not found" error.)
- Use of the MCP/plugin is subject to the Syncro API license agreement.
Claude Chat & Cowork
Claude Chat & Cowork versions install from a package file rather than a marketplace. Follow these steps to install the Syncro Service Desk plugin.
Steps
- Download the plugin.
- Click the + (plus) symbol.
- Select Manage Plugins.
- Click Add, then Upload Plugin.
- Click Browse Files, locate the plugin ZIP file, and select it.
- Click Upload. The plugin is now installed.
Result
The Syncro Service Desk plugin's skills become available in Claude. Type / or click the + button to access them.
Claude Code
To install the Syncro Service Desk plugin, enter:
/plugin marketplace add https://gitlab.com/syncromsp/syncro-open-source/syncro-plugins.git
/plugin install syncro-service-desk@syncro
The first command adds this repository as a marketplace; the second installs the package from it. syncro-service-desk@syncro names the package first and the marketplace second.
Pass the full URL including https://. The short owner/repo form is GitHub-only. To pin a specific release, append # and the tag: …syncro-plugins.git#1.0.0. (@1.0.0 is the GitHub-only form and will not work here.)
Installed this way, updates arrive on their own. See also: About Updates.
For Your Company
IT admins can deploy the package to every technician at once with a managed settings file rather than having each person install it. This assumes some familiarity with Claude Code's managed settings mechanism; if that's new to you, your Claude Code admin or IT team can help set it up.
Here's the JSON:
{
"extraKnownMarketplaces": {
"syncro": {
"source": {
"source": "url",
"url": "https://gitlab.com/syncromsp/syncro-open-source/syncro-plugins.git"
}
}
},
"enabledPlugins": {
"syncro-service-desk@syncro": true
}
}Note the source type is url. Anthropic's own example uses a github source, which will not resolve against this repository.
The file goes in the system location for the operating system:
| OS | Path |
|---|---|
| macOS | /Library/Application Support/ClaudeCode/managed-settings.json |
| Linux and WSL | /etc/claude-code/managed-settings.json |
| Windows | C:\Program Files\ClaudeCode\managed-settings.json |
Claude Code does NOT read C:\ProgramData\ClaudeCode\managed-settings.json. A policy placed there produces no error and simply does not apply, which looks like a failed deployment.
If you already maintain a managed settings file, do not edit it. Instead, drop a 20-syncro.json into managed-settings.d/ alongside it. Where two files define extraKnownMarketplaces, a later entry with the same name replaces the earlier one entirely.
After deploying, run /status on one machine and confirm the Setting sources line reads "Enterprise Managed Settings (File)" before rolling out to the fleet. MDM and Group Policy are alternatives to the file and take precedence over it where both are present. See Anthropic's managed-settings documentation.
To verify that the Syncro Service Desk plugin works, invoke /onsite-visits and name an Organization you know has open tickets. It's read only, so there is nothing to undo. If the connector is not connected, the skills say so and stop rather than guessing. If it still doesn't respond as expected, see Troubleshoot MCP Connections.
About the Plugin
Capabilities & Permissions
The skills in the Syncro Service Desk plugin act with the access you already have. The connector signs you in as yourself, and your Syncro user permissions determine what it can do: the plugin does not grant new access, it lets your AI assistant work with access you already hold.
Within that, the connector can create and update real records in your live Syncro account, including tickets, Organizations, contacts/End Users, assets, invoices and appointments, and it can send invoice email to your customer Organizations.
The skills are deliberately narrower than that: onsite-visits and doc-search have no write path at all. call-to-ticket and ticket-researcher can both write, but narrowly. call-to-ticket shows you the complete ticket and note, then waits for an explicit Yes before creating anything. ticket-researcher only writes when you explicitly ask it to, saving its findings as an AI-labeled private note that is never visible to the end user.
Extending the Plugin for Your Company
Skills are plain SKILL.md files. Nothing stops you from writing your own to sit alongside the Syncro Service Desk plugin for workflows specific to your organization, using the same Syncro MCP connector this plugin declares. For the full picture of what that connector can do, see Syncro MCP Prompt Library and Syncro MCP Tools Reference.
This is different from editing the Syncro Service Desk plugin's own skills directly: these skills are versioned and rebuilt from Syncro's repository, so local edits get overwritten on the next update, and won't match what Support expects when you report an issue against a specific plugin version.
Updates
Updates are manual for Claude Chat & Cowork. Download the newer release and upload it the same way you installed it. /onsite-visits prints its version in the header of every briefing, so you can always tell which build answered you.
For Claude Code, new versions arrive on their own: the marketplace is checked in the background and a new release is picked up without you doing anything. To pull one immediately, enter: /plugin marketplace update
If an update does not seem to have worked, check for a second copy first. A package can be installed from more than one place at once (an organization plugin store and your personal store), and if both hold this package the older copy can win, with nothing warning you. A stale copy does not error; it answers confidently from older instructions.
List your installed plugins with /plugin and remove any personal-store copy before assuming the update failed.
Access Available Skills
When first invoking a skill, authorize the Syncro connector by signing in with your Syncro credentials. Access is restricted to your organization and user permissions. See Connect the Syncro MCP Server.
Tip: Type / to view and select a skill, or enter your request in plain language.
| Name | Command | Description | Example |
|---|---|---|---|
|
Convert a Call to a Ticket
|
/call-to-ticket |
Parses call details to match customer Organization, contact/End User, and asset data, assigns priority, and drafts a private note. Requires user confirmation before writing to Syncro.
Note: This is the only skill in the Syncro Service Desk plugin that writes to Syncro. |
/call-to-ticket I just got off the phone with Bob Ulmer, his docking station won't drive his monitor. |
| Documentation Center Search | /doc-search | Searches Syncro's Documentation Center to provide product configuration details and step-by-step navigation paths. | /doc-search Does Syncro support SSO for the End User Portal? |
| Prep for Onsite Visits | /onsite-visits | Queries unresolved work orders at a specified client location to identify additional physical tasks before traveling. | /onsite-visits I'm heading to Ulmer Auction tomorrow. What else needs attention while I'm there? |
| Ticket Research Assistant | /ticket-researcher |
Analyzes asset specifications, historical ticket logs, and documentation to generate a ranked list of diagnostic steps.
Note: This skill is read-only by default. On request, it can save its findings to the ticket as an AI-labeled private note. |
/ticket-researcher Help me with ticket 4267. |
Uninstall the Plugin
Claude Chat & Cowork
- Click the + (plus) symbol.
- Select Manage Plugins.
- Locate the plugin.
- Open the plugin.
- Click Uninstall from the ellipsis menu. The plugin is now uninstalled.
Claude Code
To install the plugin, enter:
/plugin uninstall syncro-service-desk@syncro
To stop tracking this marketplace entirely, remove it with /plugin marketplace remove syncro.
Provide Feedback & Get Help
Have feedback, a skill idea that doesn't exist yet, or something of your own worth sharing? The Syncro Community is the place for it.
Report any problems to Syncro Support. When you get in touch, include the plugin version, which skill you were using, and what you asked for. Those three things are what support needs first.