MSP Claude Plugins
One command to supercharge Claude Code for MSP workflows.
/plugin marketplace add WYRE-AI/msp-claude-plugins
Then restart Claude Code. That's it.
Potencia tu agente
Instalación del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
Aún no hay una versión empaquetada en el registro. Sigue el README del repositorio.
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDel publicador
One command to supercharge Claude Code for MSP workflows.
/plugin marketplace add WYRE-AI/msp-claude-plugins
Then restart Claude Code. That's it.
The community-driven Claude Code plugin marketplace for MSPs — 70+ plugins across PSA, RMM, security, documentation, and accounting, plus cross-vendor industry workflow packs (ops, security, finance, compliance, sales, DevOps, cloud infra) that compose whatever tools you have connected.
Documentation: mcp.wyre.ai
83 vendor-specific plugins with domain knowledge for PSA, RMM, documentation, security, accounting, CRM, and productivity tools — the count keeps growing, so treat marketplace.json as the source of truth and mcp.wyre.ai as the browsable catalog. The table below highlights the most commonly used integrations, not the full list:
Plus shared skills for MSP terminology, ticket triage, cross-vendor incident correlation, and billing reconciliation.
Maturity status for the plugins listed above (not the full catalog — see marketplace.json for all 83):
Maturity levels: ✅ Production — used in real MSP environments with comprehensive coverage. 🔨 Beta — functional with core features, feedback welcome. 🚧 Alpha — early implementation, expect gaps.
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-AI/msp-claude-plugins/main/msp-claude-plugins/wyre-gateway/install.sh | bash
Claude Desktop (Windows):
irm https://raw.githubusercontent.com/WYRE-AI/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.
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.
Plugins are just markdown files. They provide:
/create-ticket and /search-ticketsWhen you ask "create a high priority ticket for Acme Corp", Claude knows:
Each plugin consists of three layers:
Most contributions touch skills and commands. MCP server changes are more involved and benefit from familiarity with the vendor's API.
Want just one vendor? Add the marketplace once, then install plugins individually:
/plugin marketplace add WYRE-AI/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
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-AI/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.
Each plugin uses environment variables for authentication. See the plugin's README:
We welcome contributions at every level — from typo fixes to new platform plugins. See CONTRIBUTING.md for our tiered contribution guide.
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.
This project is maintained by WYRE AI, a Chattanooga-based MSP focused on AI enablement.
Thanks to these wonderful people who have contributed to the MSP Claude Plugins ecosystem:
This project follows the All Contributors specification. Contributions of any kind welcome!
Apache 2.0 — see LICENSE.
Built by MSPs, for MSPs.
The community-driven Claude Code plugin marketplace for MSPs — 70+ plugins across PSA, RMM, security, documentation, and accounting, plus cross-vendor industry workflow packs (ops, security, finance,
Resumen general
The community-driven Claude Code plugin marketplace for MSPs — 70+ plugins across PSA, RMM, security, documentation, and accounting, plus cross-vendor industry workflow packs (ops, security, finance, compliance, sales, DevOps, cloud infra) that compose whatever tools you have connected.
Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
Msp Claude Plugins se ejecuta localmente por stdio.
Última comprobación: 2026-11-16. The community-driven Claude Code plugin marketplace for MSPs — 70+ plugins across PSA, RMM, security, documentation, and accounting, plus cross-vendor industry workflow packs (ops, security, finance, compliance, sales, DevOps, cloud infra) that compose whatever tools you have connected.