MCP.Market

ConnectWise Automate MCP server

by WYRE-AI·io.github.WYRE-AI/connectwise-automate-mcp·v2.0.4·1 stars

MCP server for ConnectWise Automate RMM — computers, clients, alerts, and scripts.

B70/100grade B
What users say
No reviews yet
Be the first
Safety scan
B70/100

not scanned yet

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed ConnectWise Automate yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

ConnectWise Automate tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How ConnectWise Automate compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
70/100
higher than 35% of 48,255 servers
GitHub stars
1
more than 65% of 28,688 servers

Release history: 4 versions in the registry since 2026-09-10, latest 2026-10-14, typically one every 12 days.

Install ConnectWise Automate in Claude Code, Cursor or VS Code

claude mcp add connectwise-automate-mcp -- docker run -i --rm ghcr.io/wyre-ai/connectwise-automate-mcp:v2.0.4
Add to Cursor

What the publisher says

From the ConnectWise Automate repository's README, as published. We do not edit it. Read it on GitHub

ConnectWise Automate MCP Server

A Model Context Protocol (MCP) server for ConnectWise Automate with decision tree architecture for Claude.

One-Click Deployment

[!IMPORTANT]

Before you click: this server depends on @wyre-ai/node-connectwise-automate,

which is hosted on the GitHub Packages npm registry. GitHub Packages has no

anonymous access — even though the package is public, every npm install needs a

token. The cloud builder runs npm install for you, so you must give it one, or

the build fails with npm error 401 Unauthorized ... npm.pkg.github.com.

1. Create a GitHub Personal Access Token with the read:packages scope

(classic token).

Any GitHub account works — you do not need to be a member of the

WYRE-AI org to read its public packages.

2. Add it as a build variable when prompted by the deploy flow:

- Cloudflare Workers → set a build variable named NODEAUTHTOKEN to your PAT

(Workers → Settings → Build → Variables and Secrets).

- DigitalOcean App Platform → set an encrypted env var named GITHUBTOKEN**

with scope Build Time to your PAT (the .do/deploy.template.yaml already declares it).

[!NOTE]

The DigitalOcean target builds the full Docker image and runs the complete MCP

server over HTTP — this is the recommended path for operators. This repo has no

Cloudflare Workers entrypoint (src/worker.ts), so the Workers button is not a

supported target yet; prefer DigitalOcean or the prebuilt container image

(ghcr.io/wyre-ai/connectwise-automate-mcp).

Features

  • Decision Tree Architecture: Navigate between domains (computers, clients, alerts, scripts) to access relevant tools
  • Lazy Loading: Client initialization and domain handlers are loaded on demand
  • Comprehensive API Coverage: Manage computers, clients, alerts, and scripts
  • Interactive Device Card (MCP Apps): cwautomatecomputersget renders as a read-only interactive card in MCP Apps hosts (Claude Desktop/web); neutral by default, brandable via window.BRAND injection or MCPBRAND env vars; plain-JSON behavior is unchanged in other hosts

Installation

This package is published to the GitHub Packages npm registry, which requires a token even for public packages. Authenticate once, then install:

# Authenticate npm to GitHub Packages (token needs the read:packages scope)
export NODE_AUTH_TOKEN=$(gh auth token)   # or a PAT with read:packages

npm install @wyre-ai/connectwise-automate-mcp

The repo's .npmrc already points the @wyre-ai scope at GitHub Packages and reads the token from NODEAUTHTOKEN, so no further config is needed.

Configuration

Set the following environment variables:

Authentication methods

The server supports both ConnectWise Automate authentication methods:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

ConnectWise Automate: common questions

Is ConnectWise Automate MCP server safe?
Mostly: it is graded B (70/100). Read the ConnectWise Automate safety report
How do I install ConnectWise Automate?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does ConnectWise Automate need an API key?
Yes. The registry entry asks for CW_AUTOMATE_CLIENT_ID, CW_AUTOMATE_PASSWORD, CW_AUTOMATE_2FA_CODE.
Is ConnectWise Automate maintained?
The last commit was 37 days ago (2026-09-28). The latest release is v2.0.4.
How does ConnectWise Automate compare with other MCP servers?
safety score 70/100 (higher than 35% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers). Full comparison.

More from WYRE-AI →