Installation

Choose the setup path that fits your workflow. Most users only need the MCP Gateway — plugins and skills are delivered automatically through it.

Option 1: MCP Gateway (Recommended)

If you set up the MCP Gateway, you are already done. The gateway provides all vendor tools (tickets, devices, alerts, etc.) through a single connection — there is nothing extra to install. Skills and commands from the plugin catalog are included automatically.

See the Gateway setup guide for Claude Code, Claude Desktop, and Claude.ai configuration instructions.

Option 2: Claude.ai Connectors (No CLI Needed)

Claude Pro, Team, and Enterprise users can add plugins directly from claude.ai without any command-line tools:

  1. Open claude.ai and click Customize in the left sidebar
  2. Click Connectors
  3. Click the + button, then Add custom connector
  4. Enter a name (e.g. MSP Gateway)
  5. Enter the Remote MCP server URL: https://mcp.wyretechnology.com/v1/mcp
  6. Click Add
  7. Complete the OAuth login flow when prompted

After setup, all your connected vendors are available immediately in any conversation. The same flow works in Claude Desktop via Settings → Connectors → Add Connector.

Option 3: Plugin Marketplace (Skills & Commands Only)

If you want the plugin skills and slash commands without the gateway (for example, to use with local MCP servers or just for the domain knowledge), you can install them from the Cowork marketplace.

Install All Plugins

/plugin marketplace add wyre-technology/msp-claude-plugins

Then restart Claude Code to activate the plugins.

Install Individual Plugins

If you only need specific plugins, install them individually:

/plugin marketplace add wyre-technology/msp-claude-plugins --plugin kaseya-autotask
/plugin marketplace add wyre-technology/msp-claude-plugins --plugin kaseya-it-glue
/plugin marketplace add wyre-technology/msp-claude-plugins --plugin sentinelone

Available Plugin IDs

Plugin ID Name Vendor Category
kaseya-autotaskAutotask PSAKaseyaPSA
kaseya-datto-rmmDatto RMMKaseyaRMM
kaseya-it-glueIT GlueKaseyaDocumentation
kaseya-rocketcyberRocketCyberKaseyaSecurity
ateraAteraAteraRMM + PSA
halopsaHaloPSAHaloPSA
superops-aiSuperOps.aiSuperOpsPSA + RMM
connectwise-psaConnectWise PSAConnectWisePSA
connectwise-automateConnectWise AutomateConnectWiseRMM
syncro-mspSyncro MSPSyncroPSA + RMM
ninjaone-rmmNinjaOne RMMNinjaOneRMM
huduHuduHuduDocumentation
liongardLiongardLiongardDocumentation
sentineloneSentinelOneSentinelOneSecurity
huntressHuntressHuntressSecurity
blumiraBlumiraBlumiraSecurity
knowbe4KnowBe4KnowBe4Email Security
spamtitanSpamTitanTitanHQEmail Security
m365Microsoft 365MicrosoftProductivity
pax8Pax8Pax8Marketplace
pandadocPandaDocPandaDocSales
quickbooks-onlineQuickBooks OnlineIntuitAccounting
xeroXeroXeroAccounting
salesbuildrSalesbuildrSalesbuildrCRM

Option 4: Manual Installation (Advanced)

For developers who want to contribute or modify plugins, you can install manually:

# Clone the repository
git clone https://github.com/wyre-technology/msp-claude-plugins.git

# Navigate to a specific plugin
cd msp-claude-plugins/kaseya/autotask

# Install as local plugin
claude plugin add .

Verify Installation

After installation, verify the plugins are active:

# List installed plugins
/plugins

# Check a specific skill is available
/skill kaseya-autotask:tickets

Updating Plugins

To update to the latest version:

/plugin marketplace update wyre-technology/msp-claude-plugins

Uninstalling

To remove the plugins:

/plugin marketplace remove wyre-technology/msp-claude-plugins

To remove the gateway MCP server:

claude mcp remove msp-mcp-gateway

Troubleshooting

Plugins not appearing after install

Make sure to restart Claude Code after installation. The plugins only become active after a restart.

Command not found errors

Verify the plugin is installed with /plugins. If listed but commands don't work, try reinstalling the specific plugin.

Gateway OAuth prompt doesn't appear

Try removing and re-adding the MCP server: claude mcp remove msp-mcp-gateway then re-run the add command.

API authentication errors (standalone plugins)

When running plugins without the gateway, each plugin requires vendor API credentials set as environment variables. Check the specific plugin documentation for required variables.