AI for MSPs
AI for MSPs: the skeptic's guide
The MSP community is rightly allergic to AI hype — every vendor deck since 2023 has had the same slide, and most of it describes features nobody asked for. But the skepticism now coexists with quiet adoption: the Kaseya 2026 MSP Benchmark report found 53% of MSPs already use AI in operations, and ScalePad's Copilot entered open beta in June 2026. The question stopped being "whether" a while ago.
The useful question is where. This guide draws the line the way a skeptic would: where AI is already earning its keep in an MSP, where it's a liability wearing a feature's clothes, and one principle that separates the two.
Where AI is already useful (2026)
The pattern across all three: internal audience, a human edit before anything ships, and source data close enough to check.
Ticket summarization
Condensing a forty-comment ticket thread into three sentences before an escalation or a handoff. Low stakes (the source thread is right there to check), high frequency, and the time saved is real. This is where most MSPs quietly started.
QBR narrative drafting
Turning computed service metrics into an executive summary a business owner will read. The numbers must come from the PSA — arithmetic, not generation — and the draft must be editable before a client sees it. Done that way, it removes the blank-page hour from every review.
Meeting prep
A brief before a client call: what changed since the last review, what was recommended, what they approved or declined. Useful precisely when it's grounded in recorded history — and generic when it isn't. A brief that isn't reading from a real commitment ledger is a horoscope.
Where it's dangerous
The inverse pattern: external audience, no human in the loop, or numbers with no source.
Client-facing chat
A bot answering your clients' questions about their own environment is an employee you've never supervised, speaking in your name, to the people who pay you. When it's wrong — and it will sometimes be wrong — it's wrong in front of your client's client. That's unrecoverable in a way an internal mistake never is.
Invented metrics
Language models are fluent number producers and unreliable number knowers. Any workflow where a model can originate a figure that reaches a client — an SLA percentage, an asset count, a budget line — is a liability with a delay timer. Numbers must be computed from source data, always.
Auto-execution
AI that closes tickets, changes configurations, or emails clients without a human decision in between. The MSP community's instinct here — 'read-only tools, suggest, don't execute' — is correct. An assistant that can only look and suggest can embarrass you; one that can act can take down a client.
The read-only principle
One rule captures most of the safety judgment: give AI read access and suggestion rights, never execution rights. A model that can read your PSA data can save you hours; a model that can write to it can create work — or damage — you won't find until a client does. And log every access, because "what did the AI look at?" is a question you will eventually need to answer.
The companion rule, for anything a client might see: numbers computed, words generated. The model may draft prose around figures; it may never originate a figure. This is the spine of how we think about QBR automation, and it's a useful test for any vendor: ask which numbers in their output come from arithmetic and which come from a model. A good vendor answers instantly.
MCP, concretely
MCP (Model Context Protocol) is an open standard that lets AI assistants call tools exposed by other software. Instead of exporting a CSV and pasting it into a chat, your assistant asks the system directly — with exactly the access the system chooses to expose. That last clause is where the design philosophy shows.
QBR Studio ships an MCP server built on the principles above: read-only by construction, scoped per client, and audit-logged on every call. It exposes four tools:
| Tool | Returns |
|---|---|
| list_clients | the clients in your workspace |
| client_metrics | computed service metrics for one client and period |
| get_report | a published report's contents |
| refresh_budget | the computed hardware-refresh budget from synced asset data |
It works with Claude and Claude Desktop out of the box, read-only API keys are included on every plan, and the server is open source — you can read exactly what it can and cannot do before you connect anything. Ask your assistant "what changed for this client since last quarter?" and it reads the computed metrics and the commitment ledger; it cannot touch either.
Where this leaves an MSP in 2026
Adopt the boring wins — summarization, drafting, prep — under the two rules: read-only access, and numbers computed, words generated. Skip anything client-facing or self-executing until someone shows you a failure mode you can live with. If you want to see the drafting-not-inventing approach applied to the highest-stakes document an MSP produces, the live sample QBR is generated exactly that way, and the QBR software guide covers the tooling landscape around it.
FAQ
Do MSPs actually need an 'AI strategy'?
Mostly no. They need positions on three questions: where AI drafts (internal text a human edits), where it's banned (client-facing output and anything numeric), and what access it gets (read-only). Answer those and the rest is tool selection, not strategy.
What is MCP in one paragraph?
Model Context Protocol — an open standard that lets AI assistants like Claude call tools exposed by other software. Instead of pasting exports into a chat window, the assistant queries the system directly, with the access the server chooses to grant. For MSP tooling, the interesting design decision is exactly what access that is.
Is it safe to point Claude at client data?
It depends entirely on the plumbing. Read-only, scoped, audit-logged access to computed data (the QBR Studio MCP approach) means the worst case is a wrong sentence you catch on review. Write access or raw credential sharing is a different risk class entirely. Ask any vendor: can the AI change anything, and is every access logged?
Will AI replace QBRs or the people running them?
It replaces the assembly work — pulling numbers, building decks, reconstructing history. The meeting where a human explains what the numbers mean for the client's business is the part clients are paying for, and no one has automated trust yet.
Numbers computed. Words generated. Reviews prepared.