connectwise-command-mcp

ConnectWise Command MCP server — exposes the ConnectWise Command (Continuum) ITSupport247 Reporting API as MCP tools.

Naming note: app.mspbots.ai calls this integration "ConnectWise Command (continuum)" (sys_integration.subject_code = CONTINUUM). ConnectWise acquired Continuum and rebranded its RMM product as "ConnectWise Command"; the underlying API is still hosted on the legacy ITSupport247 domain (itsupport247.net) and documented as the "Reporting API". This server wraps that Reporting API only — it is unrelated to ConnectWise Manage (PSA) or ConnectWise Automate.

Overview

This server implements the Model Context Protocol (Streamable HTTP/SSE transport) and wraps every resource in the official "Reporting API REST Resources" reference for ConnectWise Command / Continuum. It follows the MSPbots Vendor MCP Service SOP: stateless, no stored credentials, per-request header authentication.

The underlying API authenticates via HTTP Basic Auth (blank username, API key as password) and returns JSON. This server never stores the key — the caller passes it per-request via a header. All request/response field names below are transcribed verbatim from the official reference doc, not guessed.

Related MCP server: nable-rmm-mcp

Quick Start

Docker (recommended)

docker compose up --build

The server starts on http://localhost:8080.

Local (uv)

uv sync
python -m connectwise_command_mcp

Health Check

curl http://localhost:8080/health
# {"status": "ok", "service": "connectwise-command-mcp", "transport": "http"}

No token is required for the health endpoint.

授权参数说明 (Authentication)

Every request to /mcp must include the following HTTP header:

Internally, this server encodes the key as:

Authorization: Basic base64(":" + api_key)

Unlike some other RMM vendors (e.g. N-able), ConnectWise Command's Reporting API hosts are fixed public endpoints, not per-tenant — there is no "URL" field/header to configure, matching the single "API Key" field on the app.mspbots.ai integration form. Missing X-ConnectWise-Command-Api-Key returns 401 Unauthorized.

Environment Variables

MCP Endpoint

POST http://localhost:8080/mcp

Connect your MCP client with:

• Transport: http (Streamable HTTP / SSE)

• Header: X-ConnectWise-Command-Api-Key: <api_key>

Tool List

21 tools, trimmed down from an original 41-tool full-API build (2026-08-04). MSPbots' own stored integration config for this vendor calls 19 endpoints (confirmed via web/int/sys/integration/api/list against integration id 1424565871921713153), spanning Antivirus (7 of 7 kept — every antivirus tool is actually used), Patches (4 of 4 kept — same), Warranty (3 of 3 kept — same), Sites/Devices (2 of 3 actually used, kept all 3 since the category is small), Agent/System/Software (3 of 3 kept — same), plus a single Misc tool (get_score_summary, the one Misc endpoint actually used). Everything else from the original 41-tool build — Performance (7), Availability (3), Recover for Continuity/Backup (4), and the other 6 Misc tools (noncompliant mobile devices, OS summary, service requests by month/week, SNMP devices, work summary) — was removed as unused by MSPbots. If a removed tool is needed later, the official "Reporting API REST Resources" doc (linked below) still documents it and it can be re-added the same way the kept tools were generated.

Most kept tools take site_code (get one from connectwise_command_get_sites first) plus month/year (int); several also take resource_type ("desktop" or "server", per-resource restrictions noted where the doc fixes it to one value).

Sites, Devices & Summary

Agent / System / Software

Antivirus

Patches

Warranty

Misc

测试示例 (Test Example)

List all sites, then get devices for one:

{
  "method": "tools/call",
  "params": { "name": "connectwise_command_get_sites", "arguments": {} }
}

Equivalent curl against the running server (streamable HTTP MCP endpoint):

curl -X POST http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "X-ConnectWise-Command-Api-Key: <api_key>" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": { "name": "connectwise_command_get_sites", "arguments": {} }
  }'

A month/year-based resource:

{
  "method": "tools/call",
  "params": {
    "name": "connectwise_command_get_cpu_utilization",
    "arguments": { "site_code": "AGTSolutions", "month": 4, "year": 2015 }
  }
}

API Reference

• Official docs (ITSupport247 portal, Admin > Integration > Reporting API):

  • "Getting Started with the Reporting API"

  • "Reporting API REST Resources" (full per-resource request/response schemas — source of every field name in this server)

Implementation Notes

• Trimmed from 41 to 21 tools on 2026-08-04. The original build covered every resource in the official Reporting API doc. A later scope decision cut this back to MSPbots' actually-configured 19 endpoints plus the small always-kept Sites/Devices/Agent/System categories — see the Tool List section above for the exact rationale and the full list of removed tools (Performance, Availability, Recover for Continuity/Backup, and 6 of 7 Misc tools — 17 tools total). If a removed tool is needed later, the official Reporting API doc (linked below) still documents it and it can be re-added the same way the kept tools were generated.

• Error shape varies by resource — some responses use "Error" (capital, e.g. Agent Details), most use "error" (lowercase, e.g. Antivirus Summary), and the position in the response varies (top, bottom, or nested per-item). ContinuumClient._parse checks both casings.

• GET resources (Sites, Devices) return a bare JSON array, not an object with an error key.

• Request field name MachineID (used in the request body for Antivirus Version Summary, Installed Software, System Information) differs in casing from the response field MachineId — both confirmed verbatim from the official doc.

• get_site_installation_package-equivalent functionality does not exist for this API; not applicable here (unlike N-able RMM).