connectwise-asio-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@connectwise-asio-mcpshow me all companies"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 every resource in the official ConnectWise Platform APIs OpenAPI 3.0 spec (v2.7.7, 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).
Quick Start
Docker (recommended)
docker compose up --buildThe server starts on http://localhost:8080.
Local (uv)
uv sync
python -m connectwise_asio_mcpHealth 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:
Header | 类型 | 是否必填 | 默认值 | 枚举值 | 字段描述 | Example |
| string | 必填 | 无 | 无(自由文本) | OAuth2 bearer access token,由调用方(Agent Platform / 上游网关)通过 |
|
| string | 可选 |
|
| ConnectWise Asio 按账号所属地区分 3 个独立服务器(Client ID 前缀 0e30=NA/0e31=EU/0e32=AU 可判断地区);不带该 header 时用环境变量默认值,网关同时服务多地区租户时按请求覆盖。 |
|
Missing X-ConnectWise-Asio-Token returns 401 Unauthorized.
Environment Variables
Variable | Default | Description |
|
| Listening port |
|
| Listening host |
|
| Default regional server; override per-request with |
MCP Endpoint
POST http://localhost:8080/mcpConnect 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
104 tools — full coverage of every operation in the official ConnectWise Platform APIs spec (POST /v1/token, the token endpoint itself, is not exposed as a tool since the gateway handles OAuth token exchange, not this server).
Companies & Contacts (13)
Tool | 功能 | 参数 |
| 列出全部公司 | 无 |
| 新建公司(写操作) |
|
| 按 ID 查公司 |
|
| 全量替换公司(写操作) |
|
| JSON Patch 局部更新公司(写操作) |
|
| 列出公司下所有站点 |
|
| 在公司下新建站点(写操作) |
|
| 按 ID 查公司下站点 |
|
| 全量替换站点(写操作) |
|
| JSON Patch 局部更新站点(写操作) |
|
| 列出全部站点(不分公司) | 无 |
| 按 ID 查站点(不分公司) |
|
| 新建联系人(写操作) |
|
Custom Fields (11)
Tool | 功能 | 参数 |
| 列出自定义字段定义 |
|
| 新建自定义字段定义(写操作) |
|
| 按 ID 查字段定义 |
|
| 替换字段定义(写操作) |
|
| 删除字段定义(写操作) |
|
| 查公司自定义字段值 |
|
| 更新公司自定义字段值(写操作) |
|
| 查站点自定义字段值 |
|
| 更新站点自定义字段值(写操作) |
|
| 查设备自定义字段值 |
|
| 更新设备自定义字段值(写操作) |
|
Devices & Network Devices (18)
Tool | 功能 | 参数 |
| 按分类列出设备 |
|
| 查设备详情 |
|
| 查设备上运行的服务 |
|
| 批量查设备已装应用 |
|
| 查设备系统状态信息 |
|
| 查受监控的 VMware 宿主机 | 无 |
| 查 publicID/privateID 映射 |
|
| 查全部唯一服务名 | 无 |
| 查设备最新磁盘使用率 |
|
| 查设备最新内存使用率 |
|
| 查设备最新 CPU 使用率 |
|
| ⚠️批量卸载设备代理(危险写操作) |
|
| 查设备在线/离线状态 |
|
| 修改设备显示名(写操作) |
|
| 列出设备分组 | 无 |
| 新建网络设备记录(写操作) |
|
| 更新网络设备记录(写操作) |
|
| 删除网络设备记录(写操作) |
|
Policy, Policy Group & Package (11)
Tool | 功能 | 参数 |
| 列出全部策略 | 无 |
| 按 ID 查策略 |
|
| 查策略分类/子分类 |
|
| 查策略的分配情况 |
|
| 查设备的生效策略 |
|
| 查设备生效策略的覆盖项 |
|
| 列出策略组 | 无 |
| 按 ID 查策略组 |
|
| 列出全部安装包 | 无 |
| 按 ID 查安装包 |
|
| 查安装包的分配情况 |
|
Patching — OS & Third-Party (6)
Tool | 功能 | 参数 |
| 查设备补丁列表 |
|
| 批量查 OS 补丁合规汇总 |
|
| 批量查 OS 补丁详情 |
|
| 查合作伙伴补丁库存 |
|
| 批量查第三方补丁合规汇总 |
|
| 批量查第三方补丁详情 |
|
Tickets (24)
Tool | 功能 | 参数 |
| 列出工单分类 | 无 |
| 列出工单优先级 | 无 |
| 列出服务看板 |
|
| 查看板关联团队 |
|
| 列出工单来源 | 无 |
| 列出工单状态 | 无 |
| 列出工单标签 | 无 |
| 新建工单标签(写操作) |
|
| 按 ID 查标签 |
|
| 替换标签(写操作) |
|
| JSON Patch 更新标签(写操作) |
|
| 删除标签(写操作) |
|
| 查工单计数 | 无 |
| 查工单备注列表 |
|
| 新建工单备注(写操作) |
|
| 按 ID 查备注 |
|
| 替换备注(写操作) |
|
| JSON Patch 更新备注(写操作) |
|
| 列出工单类型 |
|
| 多条件搜索工单 | 30+ 个可选过滤参数(见工具 docstring),如 |
| 新建工单(写操作) |
|
| 按 ID 查工单 |
|
| 替换工单(写操作) |
|
| JSON Patch 更新工单(写操作) |
|
Alerting & Incidents (4)
Tool | 功能 | 参数 |
| 批量创建告警(写操作) |
|
| 批量更新告警(写操作) |
|
| 批量删除告警(写操作) |
|
| 上报/更新安全事件告警详情(写操作) |
|
Mapping (8)
Tool | 功能 | 参数 |
| 按 schema 查属性映射 |
|
| 查站点的集成商设备映射 |
|
| 新建/更新站点设备映射(写操作) |
|
| 全量替换站点设备映射(写操作) |
|
| 删除站点全部设备映射(写操作) |
|
| 删除单个设备映射(写操作) |
|
| 查合作伙伴全部设备映射 | 无 |
| 查站点映射列表 | 无 |
Automation (3)
Tool | 功能 | 参数 |
| 列出自动化脚本 | 无 |
| 列出 Shell 脚本 | 无 |
| 列出自动化任务 | 无 |
Backup Dashboard (4)
Tool | 功能 | 参数 |
| 关闭备份告警(写操作) |
|
| 上报备份告警记录(写操作) |
|
| 上报灾备就绪验证记录(写操作) |
|
| 上报备份运行记录(写操作) |
|
Misc (2)
Tool | 功能 | 参数 |
| 上传厂商产品用量记录(计费,写操作) |
|
| 查当前 API 速率限制状态 | 无 |
测试示例 (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, EUhttps://openapi.service.euplatform.connectwise.com, AUhttps://openapi.service.auplatform.connectwise.com
Known Gaps / Not Yet Verified
Not yet tested against a live ConnectWise Asio account — only protocol-level verification (health check, 401 on missing token,
tools/listreturning all 104 tools) has been done so far.Several request bodies with deeply nested schemas (e.g.
Company,Contact,Ticket,NetworkDevice) are exposed as a genericbody: dict/extra: dictparameter 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.connectwise_asio_uninstall_endpointsis destructive (removes RMM agents) — do not call against production data without explicit confirmation for each device.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/MSPbotsAI/connectwise-asio-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server