connectwise-asio-mcp

ConnectWise Asio MCP server — exposes the ConnectWise Platform APIs (the "Current API" behind ConnectWise Asio, formerly SolarWinds MSP/N-central-adjacent RMM) as MCP tools.

Naming note: app.mspbots.ai calls this integration "ConnectWise Asio" (sys_integration.subject_code = CWASIO). It is a distinct product from ConnectWise Command (Continuum), ConnectWise Manage (PSA), and ConnectWise Automate — each has its own MCP server in this fleet. The underlying API is officially named "ConnectWise Platform APIs" in its OpenAPI spec (developer.connectwise.com — "REST API" doc under Products > ConnectWise Platform > Platform Vendors > APIs and Callbacks).

Overview

This server implements the Model Context Protocol (Streamable HTTP/SSE transport) and wraps the ConnectWise Platform APIs — 25 tools across 5 categories (devices, companies_contacts, custom_fields, patching, automation), trimmed down to MSPbots' actually-configured 23 endpoints plus minimal core CRUD (see Tool List below; originally a full-API build of 107 operations across 24 tag categories). It follows the MSPbots Vendor MCP Service SOP: stateless, no stored credentials, per-request header authentication.

The underlying API authenticates via OAuth2 Client Credentials. This server does not perform the token exchange itself — it receives an already-obtained bearer access token per request (matching how other OAuth-flow integrations, e.g. Microsoft Graph, are handled in this MSPbots MCP fleet: the gateway mints/refreshes the token from client_id/client_secret/scope, and only the resulting token reaches this server).

Related MCP server: mcp-connectwise-psa

Quick Start

Docker (recommended)

docker compose up --build

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

Local (uv)

uv sync
python -m connectwise_asio_mcp

Health Check

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

No token is required for the health endpoint.

授权参数说明 (Authentication)

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

Missing X-ConnectWise-Asio-Token returns 401 Unauthorized.

Environment Variables

MCP Endpoint

POST http://localhost:8080/mcp

Connect your MCP client with:

• Transport: http (Streamable HTTP / SSE)

• Headers: X-ConnectWise-Asio-Token: <access_token> (required), X-ConnectWise-Asio-Base-Url: <base_url> (optional)

Tool List

25 tools, trimmed down from an original 104-tool full-API build (2026-08-04). MSPbots' own stored integration config for this vendor calls 23 endpoints across 6 underlying resource categories (devices/endpoints, companies, sites, custom fields, patching, automation) — every one of those 23 configured endpoints (including separate v1/v2 path variants, which collapse onto the same tool here) maps to a tool kept below, marked with the endpoint name it corresponds to. Everything else from the original 104-tool build (Tickets — the single largest category at 24 tools, Policy/Policy Group/Package, Mapping, Alerting & Incidents, Backup Dashboard, Misc — 6 categories, ~79 tools) was removed as unused by MSPbots. If a removed category is needed later, the vendor's OpenAPI spec (linked below) still documents its exact operations and they can be re-added the same way the kept tools were generated.

Known gap carried over from the original build: MSPbots configured two endpoints — "ConnectWise Asio Suspension" (GET /v2/alerting/suspensions) and "ConnectWise Asio Suspension Details" (GET /v2/alerting/suspensions/{ruleid}) — that have no corresponding tool in this server at all (the original 104-tool build's alerting category only ever implemented create/update/delete/post-incident operations, never a GET-suspension read). This predates the trim and was not introduced by it; flagged here since it's now more visible with the smaller tool count. See Known Gaps below.

Companies & Contacts (6)

Custom Fields (6)

Devices & Endpoints (9)

Patching (3)

Automation (1)

测试示例 (Test Example)

Get a company list, then its sites:

{
  "method": "tools/call",
  "params": { "name": "connectwise_asio_get_companies", "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-Asio-Token: <access_token>" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": { "name": "connectwise_asio_get_companies", "arguments": {} }
  }'

A parameterized call:

{
  "method": "tools/call",
  "params": {
    "name": "connectwise_asio_get_endpoint_cpu_usage",
    "arguments": { "endpoint_id": "abc-123" }
  }
}

API Reference

• Official docs (ConnectWise Developer Network — requires login): Products > ConnectWise Platform > Platform Vendors > APIs and Callbacks > REST API

• Base URLs: NA https://openapi.service.itsupport247.net, EU https://openapi.service.euplatform.connectwise.com, AU https://openapi.service.auplatform.connectwise.com

Known Gaps / Not Yet Verified

• Trimmed from 104 to 25 tools on 2026-08-04. The original build covered the full ConnectWise Platform APIs spec per an earlier scope decision. A later scope decision cut this back to MSPbots' actually-used categories — see the Tool List section above for the exact endpoint→tool mapping and the full list of the 6 removed categories (~79 tools, including the 24-tool tickets category, the single largest one in the original build). If a removed category is needed later, the vendor's OpenAPI spec (linked below) still documents its exact operations and they can be re-added the same way the kept tools were generated.

• MSPbots' configured "Suspension"/"Suspension Details" endpoints have no corresponding tool — this gap predates the trim (the original 104-tool build's alerting category never implemented a GET-suspension read operation, only create/update/delete/post-incident) and was not introduced by it. If suspension data is actually needed, this would need to be added from the vendor's OpenAPI spec.

• Not yet tested against a live ConnectWise Asio account — only protocol-level verification (health check, 401 on missing token, tools/list returning all 25 tools) has been done so far.

• connectwise_asio_update_company_custom_fields and connectwise_asio_create_company take a generic body: dict parameter rather than fully flattened named arguments — the docstring lists the required top-level fields, but nested object shapes should be cross-checked against the live API on first use.