Server data from the Official MCP Registry
MCP server for ConnectWise Automate RMM — computers, clients, alerts, and scripts.
MCP server for ConnectWise Automate RMM — computers, clients, alerts, and scripts.
Valid MCP server (3 strong, 3 medium validity signals). 2 code issues detected. 4 known CVEs in dependencies (2 critical, 1 high severity) Imported from the Official MCP Registry. 2 finding(s) downgraded by scanner intelligence.
8 files analyzed · 6 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: CW_AUTOMATE_SERVER_URL
Environment variable: CW_AUTOMATE_CLIENT_ID
Environment variable: CW_AUTOMATE_USERNAME
Environment variable: CW_AUTOMATE_PASSWORD
Environment variable: CW_AUTOMATE_2FA_CODE
Environment variable: MCP_TRANSPORT
Environment variable: AUTH_MODE
Environment variable: LOG_LEVEL
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-wyre-technology-connectwise-automate-mcp": {
"env": {
"AUTH_MODE": "your-auth-mode-here",
"LOG_LEVEL": "your-log-level-here",
"MCP_TRANSPORT": "your-mcp-transport-here",
"CW_AUTOMATE_2FA_CODE": "your-cw-automate-2fa-code-here",
"CW_AUTOMATE_PASSWORD": "your-cw-automate-password-here",
"CW_AUTOMATE_USERNAME": "your-cw-automate-username-here",
"CW_AUTOMATE_CLIENT_ID": "your-cw-automate-client-id-here",
"CW_AUTOMATE_SERVER_URL": "your-cw-automate-server-url-here"
},
"args": [
"-y",
"@wyre-technology/connectwise-automate-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
A Model Context Protocol (MCP) server for ConnectWise Automate with decision tree architecture for Claude.
[!IMPORTANT] Before you click: this server depends on
@wyre-technology/node-connectwise-automate, which is hosted on the GitHub Packages npm registry. GitHub Packages has no anonymous access — even though the package is public, everynpm installneeds a token. The cloud builder runsnpm installfor you, so you must give it one, or the build fails withnpm error 401 Unauthorized ... npm.pkg.github.com.
- Create a GitHub Personal Access Token with the
read:packagesscope (classic token). Any GitHub account works — you do not need to be a member of thewyre-technologyorg to read its public packages.- Add it as a build variable when prompted by the deploy flow:
- Cloudflare Workers → set a build variable named
NODE_AUTH_TOKENto your PAT (Workers → Settings → Build → Variables and Secrets).- DigitalOcean App Platform → set an encrypted env var named
GITHUB_TOKENwith scope Build Time to your PAT (the.do/deploy.template.yamlalready 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-technology/connectwise-automate-mcp).
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-technology/connectwise-automate-mcp
The repo's .npmrc already points the @wyre-technology scope at GitHub Packages and
reads the token from NODE_AUTH_TOKEN, so no further config is needed.
Set the following environment variables:
| Variable | Required | Description |
|---|---|---|
CW_AUTOMATE_SERVER_URL | Yes | Your ConnectWise Automate server URL (e.g. https://your-server.hostedrmm.com) |
CW_AUTOMATE_CLIENT_ID | Yes | ConnectWise Automate Client ID |
CW_AUTOMATE_USERNAME | Yes | Integrator username or user login |
CW_AUTOMATE_PASSWORD | Yes | Integrator password or user password |
CW_AUTOMATE_2FA_CODE | No | Two-factor authentication code (forces user authentication) |
CW_AUTOMATE_AUTH_METHOD | No | integrator (default) or user |
The server supports both ConnectWise Automate authentication methods:
integrator (default) – machine-to-machine integrator account. Recommended for automation. Does not use 2FA.user – interactive user login, which can supply a two-factor code.You normally don't need to set CW_AUTOMATE_AUTH_METHOD: integrator auth is used by
default, and user auth is selected automatically when CW_AUTOMATE_2FA_CODE is
provided.
Add to your Claude configuration:
{
"mcpServers": {
"connectwise-automate": {
"command": "npx",
"args": ["@wyre-technology/connectwise-automate-mcp"],
"env": {
"CW_AUTOMATE_SERVER_URL": "https://your-server.hostedrmm.com",
"CW_AUTOMATE_CLIENT_ID": "your-client-id",
"CW_AUTOMATE_USERNAME": "your-username",
"CW_AUTOMATE_PASSWORD": "your-password"
}
}
}
}
The server uses a decision tree pattern. Start by navigating to a domain:
cwautomate_navigate to select a domain (computers, clients, alerts, scripts)cwautomate_back to return to the main menu# Install dependencies
npm install
# Build
npm run build
# Run tests
npm test
# Type check
npm run typecheck
# Lint
npm run lint
Apache-2.0
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.