Claude skills for MSPs
969 skills across 16 platforms — every one named, documented, and traced when it runs. Hosted, so there is nothing to install and no API keys to hand your techs. Reach them from Claude.ai, Claude Desktop or Claude Code through one connector. Read-only by default, and on most platforms read-only by construction.
The board
Every platform, every skill counted.
A skill you can't inspect is a claim, not a capability. Each platform below links to its full skill list — what each one reads, in plain language, and what the integration can never do.
How these reach Claude
One connector, not one per product.
Anthropic's Skills are instruction folders you add to Claude itself. These are something else, and the two compose: each platform on the board is an MCP server MSPStuff hosts, and its skills teach Claude what that platform's data means to an MSP — what a stale agent looks like, which patch states matter, where the audit trail lives.
You reach them by adding Switchboard once. In Claude.ai and Claude Desktop that is Settings, then Connectors; in Claude Code it is an OAuth sign-in or a pasted key. After that, every platform your company connected sits behind that single connector, instead of a separate custom connector for each product.
Your admin scopes each person separately. Claude reads your platforms and, if the role allows, runs and creates reports in MSPStuff. Every figure Claude gives back points at the tool call that produced it, so you can audit the answer rather than trust it.
Common questions
Asked before you had to ask.
Are these the same as Claude's own Skills?
No, and they compose well. Anthropic's Skills are instruction folders you add to Claude itself. These are MSP platform skills that live on MSPStuff-hosted MCP servers — they give Claude live, scoped access to ConnectWise, Microsoft 365, Meraki, Pax8 and the rest of your stack, and teach it what that data means to an MSP.
How do these reach Claude?
Through one connector. Add Switchboard to Claude.ai or Claude Desktop under Settings, then Connectors. In Claude Code, sign in with OAuth or paste a key. Every platform your company connected is then behind that single connector; you do not add one per product.
Do I need a Claude subscription?
To use Claude as your client, yes — your own Claude plan, on your own account. You can also skip it entirely and ask the same questions inside Switchboard, which needs no separate AI subscription.
What can Claude change?
Nothing today. Claude reads your platforms; in MSPStuff it can also run and create reports when the role allows it. Any change a platform could make is held back — refused by our server before anything reaches the platform — until a person switches it on; nothing is switched on today.
Who decides what Claude can see?
Your admin, per person and per domain — service, finance, sales, company, assets, projects or people. Your connector is scoped to you, the scopes can change at any time, and disconnecting the client ends its access immediately.
What is the difference between Claude Code and Claude skills?
Claude Code is Anthropic's agentic coding tool: it reads your codebase, edits files and runs commands. Skills are folders of instructions, scripts and resources that Claude loads when a task needs them, and Anthropic lets you use them across its Claude apps, Claude Code and its API. The MSP skills on this page reach Claude Code through the same MSPStuff connector as Claude.ai; in Claude Code you sign in with OAuth or paste a key.
Is a Claude skill just a prompt?
No. Anthropic contrasts Skills with prompts, which are conversation-level instructions for one-off tasks: a skill loads on demand, so you don't repeat the same guidance in every conversation, and it can bundle scripts and resources as well as instructions. The skills on this page are different: they are MSP platform skills that live on MSPStuff-hosted MCP servers, with live, scoped access to your platforms, so they read your data rather than only describing how to think about it.
Can Claude skills use MCP?
Yes. Anthropic's help center puts it this way: you can use both together, because MCP connections give Claude access to tools while skills teach Claude how to use those tools well. MSPStuff is the MCP side for an MSP stack: one connector that reaches every platform your company connected, scoped per person by your admin.
Can Claude skills be used with Copilot?
GitHub Copilot reads skills in the same SKILL.md format: GitHub's documentation says agent skills work with Copilot cloud agent, Copilot code review, the GitHub Copilot CLI, the GitHub Copilot app and agent mode in Visual Studio Code, and it reads a repository's .claude/skills folder. The MSP skills on this page don't depend on that format, because they sit on MSPStuff-hosted MCP servers, and Microsoft Copilot Studio connects to the same MSPStuff endpoint as Claude.
Get AI connected to your stack.
Apply for the beta: 14 days free on the Hosted plan against your own environment, read-only, every answer traced. Accepted MSPs get half off seats and client tenants for the first year. Dedicated infrastructure is priced separately.