0
Current connectors
The connector set already mapped in the current build.
Connector catalog
Built for the tools MSPs actually run.
MSPlex connectors are being built against real production environments. The current build is focused on the systems MSPs already depend on, with the next launch waves queued behind it.
0
Planned for Q3
The next launch wave already being planned now.
0
Planned for Q4
Additional launch-wave coverage after the initial rollout.
Current build
Core connectors already taking shape.
The current build centers on HaloPSA, Hudu, IT Glue, ConnectWise, and PAX8. Each route is being hardened for the operational details that demos skip.
HP
PSA
Current buildHaloPSA
Full ticket lifecycle, client management, contract billing, time entries, asset tracking, and SLA monitoring.
28 toolsOAuth2Webhooks
- Ticket lifecycle management
- Client and contract lookup
- Time entries and asset tracking
- SLA and workflow visibility
Hu
Documentation
Current buildHudu
Knowledge base search, password retrieval, asset documentation, company records, and procedure lookup.
16 toolsAPI keyFull CRUD
- Knowledge base search
- Password and process lookup
- Asset documentation access
- Company and procedure records
IG
Documentation
Current buildIT Glue
Documentation search, configuration lookup, password retrieval, and company knowledge routing through the current MSPlex build.
API keyRead + Act
- Knowledge base and configuration lookup
- Password and asset retrieval
- Flexible documentation search
- Company and location records
CW
PSA
Current buildConnectWise
Ticket workflows, company records, agreement visibility, and dispatch-aware actions for ConnectWise environments.
API keyRead + Act
- Service board and ticket workflows
- Agreement and company lookup
- Member and schedule visibility
- Dispatch and status actions
P8
Procurement
Current buildPAX8
Vendor lookup, procurement context, subscription visibility, and marketplace-aware workflows for PAX8 operations.
API keyRead + Act
- Vendor and catalog lookup
- Procurement and order context
- Subscription visibility
- Cloud marketplace routing
Launch pipeline
Queued around the first public waves.
SentinelOne, Datto BCDR, and Entra ID are planned for Q3, with Microsoft 365 staged behind them for Q4 as the connector surface expands.
S1
Security
Planned Q3SentinelOne
Threat detection status, endpoint health, quarantine actions, policy management, and incident investigation.
22 toolsAPI tokenRead + Act
- Threat detection status
- Endpoint health checks
- Quarantine and policy actions
- Incident investigation support
Da
BCDR
Planned Q3Datto BCDR
Backup status, recovery point verification, screenshot checks, agent health, and restore operations.
18 toolsAPI keyRead + Act
- Backup status checks
- Recovery point verification
- Screenshot and agent health review
- Restore operation support
En
Identity
Planned Q3Entra ID
User management, group membership, license assignment, sign-in logs, and conditional access policy review.
20 toolsOAuth2Graph API
- User and group management
- License assignment
- Sign-in log visibility
- Conditional access policy review
M365
Productivity
Planned Q4Microsoft 365
Mailbox context, collaboration workflows, license visibility, and tenant productivity actions are planned for the Microsoft 365 launch wave.
OAuth2Graph API
- Mailbox and user context
- Calendar and collaboration routing
- License visibility
- Tenant productivity workflows
Connector posture
What makes an MSPlex connector production-ready.
A connector is only useful if the auth model, tenancy boundaries, and operational edge cases are already handled. That is the actual work.
Auth handled properly
OAuth2, API keys, token refresh, and tool registration are built into the connector layer instead of delegated to ad hoc scripts.
Tenant-safe by design
Every connector is designed for per-tenant credentials, usage metering, and the exchange model required by MSP environments.
Built for real workflows
The goal is not a generic tool list. It is reliable execution across tickets, docs, security posture, identity, and backup operations.
Request a connector
Tell us what your stack needs next.
If your team needs Kaseya, additional PSA coverage, NinjaOne, Sophos, or another platform, that demand should shape the roadmap after launch.
KaseyaAdditional PSANinjaOneSophos