The Syncro MCP Guide: Every Claude Plugin and Skill, and How to Use Them

Key Takeaways

• Syncro offers two Claude plugins, Syncro Service Desk and Syncro Business Owner, with five skills between them: /call-to-ticket, /ticket-researcher, /onsite-visits, /doc-search, and /qbr.
• Every skill runs on the Syncro MCP server, which is included on every Syncro plan and is limited to what each user can already do in Syncro.
• Call to Ticket creates tickets only after you approve the full draft. Ticket Research Assistant can save its findings as a private, AI-labeled note when you ask. Every other skill only reads.
• The QBR skill builds a client-ready report plus a separate internal prep sheet, so margin, overdue invoices, and SLA misses stay off the client’s copy unless you add them.
• Setup takes three steps: connect Syncro in Claude, add the Syncro plugin marketplace from GitLab, and install the plugins you want.

Connecting Claude to your PSA and RMM is the easy part. Getting every tech to use it the same way, with prompts that pull the right data and stop before they change anything, takes more work.

Syncro’s Claude plugins handle that part. Each plugin packages a set of skills: instructions that tell Claude how to do one job, like logging a call, researching a stuck ticket, or building a quarterly business review from your live Syncro data.

This guide covers every plugin and skill Syncro has released, what each one does, when to reach for it, and how to set it up. We’ll update it as new skills ship.

How the MCP Server, Plugins, and Skills Fit Together

There are three pieces of the puzzle, and each one does a different job.

• The Syncro MCP server is the connection. It connects AI tools like Claude, ChatGPT, Microsoft Copilot, and Cursor to live Syncro data: tickets, billing, alerts, assets, appointments, clients, contacts, and products.
• A skill is a set of instructions for one job. Type a slash command like /qbr, or just ask for what you need, and Claude follows the skill’s steps against your data.
• A plugin bundles related skills. You install it once, and every skill inside it is ready to use.

Skills matter because they standardize the work. When the whole team runs the same skill, your newest tech logs a call the same way your most senior one does because both are following the same instructions.

Each skill is a text file of instructions, not code. You can open one and change the note format or the priority rules to match how your team works, without a developer.

All Syncro Claude Skills at a Glance

In Claude Code, commands carry the plugin prefix, for example /syncro-service-desk:call-to-ticket.

The Syncro Service Desk Plugin

Service Desk is for the techs and dispatchers working the queue. Most of what they need to help a client is already somewhere in Syncro: a ticket a coworker closed last spring, a second open ticket at the same office, a device’s install history.

Its four skills dig that up so you don’t have to.

Call to Ticket (/call-to-ticket)

• Use it when: you just hung up with a client.
• How it works: Type /call-to-ticket and tell it what the client said. It finds the right customer, contact, and device in Syncro, picks a priority and a tech, and writes a private note. You see the whole ticket before anything is created.
• Example prompt: “/call-to-ticket Just got off the phone with Maria at Lakeside Dental. The front desk printer shows offline for everyone.”
• Write approval required

Ticket Research Assistant (/ticket-researcher)

• Use it when: you’re stuck on a ticket and you don’t want to start cold.
• How it works: Give it a ticket number. It digs through that client’s ticket history for the same issue, checks the docs, looks at an associated device’s specs and installed software, and hands back a ranked list of things to try, with why each one made the list.
  
  It sticks to the current client unless you tell it to look wider. When it searches the web, it uses only symptoms, error codes, and product versions, so client names, hostnames, and ticket text never leave Syncro. Want the findings on the ticket? Ask it to save them as a private, AI-labeled note.
• Example prompt: “/ticket-researcher What should I try next on ticket 5120?”
• Read-only unless you ask it to save a note

Onsite Visit Prep (/onsite-visits)

• Use it when: you’re heading out to a client site.
• How it works: Name the client you’re visiting. It pulls every open ticket and sorts it into work that needs you onsite, work you could pick up while you’re there, and everything else. If a coworker has a workstation move queued at the same office, you can handle it on the same trip.
• Example prompt: “/onsite-visits I’m at Lakeside Dental Thursday morning. Is anything else open there?”
• Read only

Documentation Search (/doc-search)

• Use it when: you’re unsure whether Syncro can do something.
• How it works: Ask your question and it answers from the Syncro Documentation Center instead of the open web, including where the setting lives and how to get there. No support ticket needed.
• Example prompt: “/doc-search Can Syncro auto-assign tickets based on which client submits them?”
• Read only

The Syncro Business Owner Plugin

Business Owner is built for the people who manage client relationships: MSP owners, account managers, and vCIOs. Today it includes one skill, Quarterly Business Review, with more on the way.

Quarterly Business Review (/qbr)

QBR prep takes time. In the ScalePad 2026 MSP Trends Report, 41% of MSPs put a single QBR at three to five hours of prep, and the top three pain points are building the reports and visuals (34%), making sure the data is accurate (32%), and pulling the right data together (31%). The QBR skill does the pulling for you, opening with what’s ahead and what decisions should be made instead of a recap of last quarter.

• Use it when: you have a quarterly business review on the calendar.
• How it works: Ask for a QBR for a specific client, decide what period to cover (3, 6, or 12 months, or custom dates), what to focus on, or whether to skip anything, like a server the client just replaced. The skill reads that client’s tickets, invoices, and assets, then opens a Review Console where you can review every suggested item to include or exclude, with a reason next to each exclusion.
• Example prompt: “/qbr Build a six-month QBR for Lakeside Dental and leave out the server we replaced in August.”
• Read only

Decide what the client sees, edit your recommendations, add your logo, then generate the report as an HTML file, print it to PDF, or copy the HTML to paste elsewhere.

Every QBR Report includes:

• Where the client stands today: how old the fleet is by device class, which warranties are running out (where you’ve recorded the dates), which machines run an operating system past end of support, plus antivirus coverage and disk space.
• What you handled: ticket volume against the prior period, split into requests from the client’s people and issues your monitoring caught, with typical response and resolution times.
• What you recommend: a short list of decisions, each tied back to a finding and given a deadline or trigger.

And get peace of mind knowing:

• Sensitive content stays with you: SLA misses, overdue invoices, billing gaps, and monitoring blind spots land on a separate prep sheet in the Review Console, each with a suggested way to bring it up. Margin and the receivables analysis can’t end up in the client report.
• The numbers hold up: automated alerts are counted separately from tickets your client raised, and times are reported as medians, so one ticket that sat open for weeks doesn’t distort the picture.

One tip: save the console to your computer and work from that copy, and never publish or share it, because it includes your prep sheet.

How to Set Up the Syncro Claude Plugins

The plugins work in Claude Chat, Cowork, and Claude Code, with any Claude subscription. Setup is a one-time job.

1. Connect Syncro in Claude. Go to Customize, then Connectors, find Syncro, and click Connect, then Allow Access. If your organization hasn’t approved Syncro yet, click Request to notify your Claude admins. To check that it worked, ask Claude to list your Syncro users.
2. Add the Syncro plugin marketplace. From the left sidebar, select Customize, then the Plugins tab, click +Add, choose Add Marketplace, paste https://gitlab.com/syncrosecure/syncro-plugins.git, and click Sync.
3. Install the plugins you want. Click + on Syncro Service Desk, Syncro Business Owner, or both.

In Claude Code, add the marketplace with /plugin marketplace add https://gitlab.com/syncrosecure/syncro-plugins.git, then install each plugin with /plugin install syncro-service-desk@syncro-plugins and /plugin install syncro-business-owner@syncro-plugins.

For Claude Code, IT admins can also deploy both plugins to every machine with a managed settings file. The Syncro Claude plugin guide has the full steps, including updates and uninstalling.

Rollout Tips and Current Limits

A few things to know before connecting the Syncro MCP and handing the plugins to your team.

• Audit permissions before rollout. The Syncro MCP server mirrors each signed-in user’s Syncro permissions. Whatever a tech can access in Syncro, Claude can access on their behalf, including actions they never use day to day. Review your Security Center settings first.
• Be specific when names overlap. Claude finds customers and techs from partial names, so “Acme” or “Mike” works. If more than one record matches, Claude asks which one you mean. Misspellings and nicknames may not match at all, so use the name as it appears in Syncro when in doubt.
• Keep an eye on Claude usage. In a Syncro MCP workshop demo, a full QBR for a customer with 100+ tickets used most of the remaining five-hour allowance on a Claude Pro plan. Teams that run skills all day may want a higher Claude tier.
• The MCP server can’t run scripts. Claude can write a script for you, but you must run it in Syncro yourself.
• The QBR skill doesn’t cover everything (yet). It can’t report installed software, script run history, or labor detail from individual timer entries, and patch status appears only where your account records it.
• The Onsite Visit Prep skill works one client at a time. It won’t point you to nearby clients with open work.

Connecting Your AI Tools to Your Syncro Data

The Syncro MCP server connects tools like Claude, ChatGPT, and Copilot to your Syncro data, covering the full service-to-billing workflow. It can work tickets, customers, contacts, assets, and appointments; log and charge time; and build and email estimates and convert them to invoices. It also reads RMM alerts, purchase orders, timeclock entries, and Syncro documentation.

The Claude plugins and skills turn that connection into repeatable work: a ticket logged the same way every time, a stuck ticket researched from your own history, one site visit instead of two, and a QBR that opens with what the client can act on.

Every skill works within each user’s Syncro permissions, and none of them create or change a record without you asking. That makes them safe to hand to the whole team, not just the techs who already write good prompts. Install the plugins, run one skill on a real ticket or client this week, and you’ll see where they fit in your day.

More Ways to Use the Syncro MCP

The Syncro MCP Prompt Library has copy-and-paste prompts for jobs the plugins don’t cover, like queue triage, SLA breach reviews, and unbilled time. To see the skills in action, watch the on-demand Optimizing Your Service Desk with Claude workshop, or start with our introduction to the Syncro MCP server.

Try the Syncro Claude Skills

Run your next QBR or a stuck ticket through Claude and Syncro. Start a 14-day free trial, no credit card required, or see everything the Syncro MCP server connects.

---

By

The Syncro Team

---

Share

• Share on Facebook
• Share on X
• Email this Page