MSP Claude Plugins

One command to supercharge Claude Code for MSP workflows.

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

Then restart Claude Code. That's it.

Documentation: mcp.wyre.ai

What you get

Thirty-three vendor-specific plugins with domain knowledge for PSA, RMM, documentation, security, accounting, CRM, and productivity tools:

Plus shared skills for MSP terminology, ticket triage, cross-vendor incident correlation, and billing reconciliation.

Plugin Maturity

Maturity levels: ✅ Production — used in real MSP environments with comprehensive coverage. 🔨 Beta — functional with core features, feedback welcome. 🚧 Alpha — early implementation, expect gaps.

Two Ways to Connect

Hosted Gateway (Recommended)

Use the WYRE Conduit gateway to connect your MSP tools to Claude with zero infrastructure. OAuth 2.1 + PKCE authentication, encrypted credential storage, and all 98 vendor integrations available immediately.

Claude Code (CLI):

claude mcp add --transport http msp-mcp-gateway https://conduit.wyre.ai/v1/mcp

Claude Desktop (macOS / Linux):

curl -fsSL https://raw.githubusercontent.com/wyre-technology/msp-claude-plugins/main/msp-claude-plugins/wyre-gateway/install.sh | bash

Claude Desktop (Windows):

irm https://raw.githubusercontent.com/wyre-technology/msp-claude-plugins/main/msp-claude-plugins/wyre-gateway/install.ps1 | iex

The installer scripts preserve your existing config, create a backup, and only append the gateway entry.

Start a free trial

Self-Hosted

Run MCP servers yourself for full control. Each server is available as an npm package, Docker image, or MCPB bundle for Claude Desktop.

See the Getting Started guide for installation instructions.

How it works

Plugins are just markdown files. They provide:

• Skills — Domain knowledge Claude references when helping you (API patterns, field mappings, rate limits)
• Commands — Slash commands like /create-ticket and /search-tickets

When you ask "create a high priority ticket for Acme Corp", Claude knows:

• Which API endpoint to call
• What priority values mean (varies by vendor!)
• How to authenticate
• Rate limit boundaries

Architecture

Each plugin consists of three layers:

1. Skills — Markdown files with domain knowledge (API patterns, field mappings,
   vendor terminology). Low maintenance, easy to contribute to.
2. Commands — Slash commands for common MSP workflows. Moderate complexity.
3. MCP Servers — Full server implementations that connect Claude to vendor APIs.
   These handle authentication, rate limiting, and data transformation.

Most contributions touch skills and commands. MCP server changes are more involved
and benefit from familiarity with the vendor's API.

Individual plugins

Want just one vendor? Add the marketplace once, then install plugins individually:

/plugin marketplace add wyre-technology/msp-claude-plugins
/plugin install autotask@msp-claude-plugins
/plugin install syncro@msp-claude-plugins
/plugin install halopsa@msp-claude-plugins
/plugin install liongard@msp-claude-plugins

Codex example

This PR adds Codex metadata for the Autotask plugin as a first representative
pattern for cross-harness distribution:

codex plugin marketplace add https://github.com/wyre-technology/msp-claude-plugins

Then install Kaseya Autotask from the Codex Plugins UI. The same
.codex-plugin/plugin.json and .agents/plugins/marketplace.json pattern can
be repeated for the other vendor plugins over time.

Configuration

Each plugin uses environment variables for authentication. See the plugin's README:

• Autotask — API key + integration code
• Datto RMM — API key header
• IT Glue — API key header
• Hudu — API key + base URL
• RocketCyber — Bearer API key
• Syncro — API key query param
• Atera — X-API-KEY header
• SuperOps.ai — Bearer token
• HaloPSA — OAuth 2.0 client credentials
• Liongard — Access Key ID + Secret (X-ROAR-API-KEY)
• ConnectWise Manage — Public/private key + client ID
• ConnectWise Automate — Integrator credentials
• NinjaOne — OAuth 2.0 client credentials
• SalesBuildr — API key
• Pax8 — MCP token (official hosted server)
• Xero — OAuth 2.0
• QuickBooks Online — OAuth 2.0
• Microsoft 365 — OAuth 2.0 (multi-tenant Entra ID)
• Rootly — API token (Bearer)

Contributing

We welcome contributions at every level — from typo fixes to new platform plugins.
See CONTRIBUTING.md for our tiered contribution guide.

Evals and production telemetry

The evals/autotask-psa/ directory contains a small human-review eval set for
ticket triage, time-entry drafting, and contract checks. The cases are
harness-neutral so the same plugin behavior can be checked in Claude Code,
Codex, or another agent workspace before expanding the pattern to other vendor
plugins.

If you publish plugins through Telvine, keep runtime telemetry metadata-only:
skill.invocation.start, skill.invocation.end, and skill.invocation.error
for skill behavior, plus plugin.component.invoked and
plugin.component.error for commands, MCP tools, or other non-skill components.
Do not emit prompts, customer records, tenant data, connector payloads, tool
arguments, credentials, browser captures, or model outputs.

Community

This project is maintained by WYRE AI, a Chattanooga-based
MSP focused on AI enablement.

• Questions or feedback? Open a Discussion
• Found a bug? File an Issue
• Want to contribute? See CONTRIBUTING.md
• Using this in your MSP? We'd love to hear about it — drop us a note in Discussions

Contributors

Thanks to these wonderful people who have contributed to the MSP Claude Plugins ecosystem:

Aaron Sachs 💻 🚧 🚇 📖	shaank0 💻	Om Bhavsar 💻	Vinnie Esposito 💻	Mauricio Schaepers 💻 🐛	ezwep 🤔 🐛	Chris Cooper 🐛
andrewday-sp 🐛	bionemesis 🤔

This project follows the All Contributors specification. Contributions of any kind welcome!

License

Apache 2.0 — see LICENSE.

Built by MSPs, for MSPs.