{"id":"be7c6d9a-e240-4e4b-a26c-cd75bc22db3a","slug":"connectwise-automate-mcp","kind":"mcp","name":"connectwise-automate-mcp","summary":"MCP server for ConnectWise Automate (RMM) — computer management, patching, scripting, and monitoring tools for AI assistants","owner":"WYRE-AI","repoUrl":"https://github.com/WYRE-AI/connectwise-automate-mcp","license":"Apache-2.0","licenseTier":"permissive","trust":"community","stars":1,"match":null,"fewStars":true,"format":"mcp","createdAt":"2026-02-05T16:16:21.000Z","addedAt":"2026-10-14T05:20:30.589Z","logoUrl":"https://avatars.githubusercontent.com/u/288510302?v=4","linkOnly":false,"collection":null,"skillPath":null,"categories":["cloud-infra","memory-knowledge"],"tags":["ai-tools","claude","connectwise-automate","msp","typescript","wyre-technology","msp-mcp"],"runtime":"docker","local":true,"cloudCapable":false,"cloudCapability":"unknown","cloudReadyOnPlatform":false,"needsApiKey":true,"reviewed":false,"syncedAt":"2026-10-14T19:31:28.742Z","sample":false,"url":"https://conduits.dev/tools/connectwise-automate-mcp","language":"TypeScript","transports":["stdio"],"install":{"docker":"ghcr.io/wyre-technology/connectwise-automate-mcp:v1.8.2"},"requirements":{"env":[{"name":"CW_AUTOMATE_SERVER_URL","secret":false,"required":true,"description":"ConnectWise Automate server URL (e.g. https://your-server.hostedrmm.com)"},{"name":"CW_AUTOMATE_CLIENT_ID","secret":true,"required":true,"description":"ConnectWise Automate integrator client ID"},{"name":"CW_AUTOMATE_USERNAME","secret":false,"required":true,"description":"Integrator username or user credential"},{"name":"CW_AUTOMATE_PASSWORD","secret":true,"required":true,"description":"Integrator password or user password"},{"name":"CW_AUTOMATE_2FA_CODE","secret":true,"required":false,"description":"Two-factor authentication code, if required by the account"},{"name":"MCP_TRANSPORT","secret":false,"required":false,"description":"Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting."},{"name":"AUTH_MODE","secret":false,"required":false,"description":"Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway."},{"name":"LOG_LEVEL","secret":false,"required":false,"description":"Log verbosity: debug, info, warn, error"}],"upstreamMayCharge":false},"tools":null,"readme":"# ConnectWise Automate MCP Server\n\nA Model Context Protocol (MCP) server for ConnectWise Automate with decision tree architecture for Claude.\n\n## One-Click Deployment\n\n> [!IMPORTANT]\n> **Before you click:** this server depends on `@wyre-ai/node-connectwise-automate`,\n> which is hosted on the **GitHub Packages** npm registry. GitHub Packages has no\n> anonymous access — even though the package is public, every `npm install` needs a\n> token. The cloud builder runs `npm install` for you, so you must give it one, or\n> the build fails with `npm error 401 Unauthorized ... npm.pkg.github.com`.\n>\n> 1. Create a GitHub **Personal Access Token** with the `read:packages` scope\n>    ([classic token](https://github.com/settings/tokens/new?scopes=read:packages&description=connectwise-automate-mcp%20deploy)).\n>    Any GitHub account works — you do **not** need to be a member of the\n>    `WYRE-AI` org to read its public packages.\n> 2. Add it as a build variable when prompted by the deploy flow:\n>    - **Cloudflare Workers** → set a build variable named **`NODE_AUTH_TOKEN`** to your PAT\n>      (Workers → Settings → Build → Variables and Secrets).\n>    - **DigitalOcean App Platform** → set an encrypted env var named **`GITHUB_TOKEN`**\n>      with scope **Build Time** to your PAT (the `.do/deploy.template.yaml` already declares it).\n\n[![Deploy to DO](https://www.deploytodo.com/do-btn-blue.svg)](https://cloud.digitalocean.com/apps/new?repo=https://github.com/WYRE-AI/connectwise-automate-mcp/tree/main)\n\n[![Deploy to Cloudflare Workers](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/WYRE-AI/connectwise-automate-mcp)\n\n> [!NOTE]\n> The DigitalOcean target builds the full Docker image and runs the complete MCP\n> server over HTTP — this is the recommended path for operators. Set\n> `CONDUIT_S2S_SECRET` (and the `CW_AUTOMATE_*` secrets) before the first boot;\n> HTTP mode exits if the S2S secret is missing. The template sets `AUTH_MODE=env`\n> for that single-tenant deploy. This repo has no supported Cloudflare Workers\n> target yet; prefer DigitalOcean or the prebuilt container image\n> (`ghcr.io/wyre-ai/connectwise-automate-mcp`).\n\n## Features\n\n- **Decision Tree Architecture**: Navigate between domains (computers, clients, alerts, scripts) to access relevant tools\n- **Lazy Loading**: Client initialization and domain handlers are loaded on demand\n- **Comprehensive API Coverage**: Manage computers, clients, alerts, and scripts\n- **Interactive Device Card (MCP Apps)**: `cwautomate_computers_get` renders as a read-only interactive card in MCP Apps hosts (Claude Desktop/web); neutral by default, brandable via `window.__BRAND__` injection or `MCP_BRAND_*` env vars; plain-JSON behavior is unchanged in other hosts\n\n## Installation\n\nThis package is published to the **GitHub Packages** npm registry, which requires a\ntoken even for public packages. Authenticate once, then install:\n\n```bash\n# Authenticate npm to GitHub Packages (token needs the read:packages scope)\nexport NODE_AUTH_TOKEN=$(gh auth token)   # or a PAT with read:packages\n\nnpm install @wyre-ai/connectwise-automate-mcp\n```\n\nThe repo's `.npmrc` already points the `@wyre-ai` scope at GitHub Packages and\nreads the token from `NODE_AUTH_TOKEN`, so no further config is needed.\n\n## Configuration\n\nCopy [`.env.example`](.env.example) and set the variables below. The stdio transport reads `CW_AUTOMATE_*` and does not use `CONDUIT_S2S_SECRET`.\n\n| Variable | Required | Description |\n|----------|----------|-------------|\n| `CW_AUTOMATE_SERVER_URL` | For stdio and `AUTH_MODE=env` | ConnectWise Automate server URL (e.g. `https://your-server.hostedrmm.com`) |\n| `CW_AUTOMATE_CLIENT_ID` | For stdio and `AUTH_MODE=env` | ConnectWise Automate Client ID |\n| `CW_AUTOMATE_USERNAME` | For stdio and `AUTH_MODE=env` | Integrator username or user login |\n| `CW_AUTOMATE_PASSWORD` | For stdio and `AUTH_MODE=env` | Integrator password or user password |\n| `CW_AUTOMATE_2FA_CODE` | No | Two-factor authentication code (forces `user` authentication) |\n| `CW_AUTOMATE_AUTH_METHOD` | No | `integrator` (default) or `user` |\n| `MCP_TRANSPORT` | No | `stdio` (default) or `http` |\n| `AUTH_MODE` | No | `gateway` (Docker image and Compose default) or `env`. Gateway mode requires `X-CWA-Server`, `X-CWA-Client-ID`, `X-CWA-Username`, and `X-CWA-Password` on each `/mcp` request and never falls back to `CW_AUTOMATE_*`. `env` uses those variables only after S2S auth succeeds. |\n| `CONDUIT_S2S_SECRET` | Yes for HTTP | Service-to-service secret. Generate with `openssl rand -hex 32`. The HTTP server logs an error and exits non-zero when this is empty or a known placeholder (`replace-with-a-real-secret`, `changeme`, and the other example values). The value is never logged. Compose will not start without it. Never commit a real value. |\n| `MCP_ALLOW_INSECURE_DEV` | No | Set to exactly `1` only for local development to start HTTP without `CONDUIT_S2S_SECRET`. The process logs a warning and does not enforce `X-Gateway-S2S`. The listener is forced to `127.0.0.1`; a wider `MCP_HTTP_HOST` (including `0.0.0.0`) is ignored and the override is logged. A placeholder secret still refuses to start. |\n| `MCP_HTTP_HOST` | No | Bind address when `MCP_TRANSPORT=http` and `CONDUIT_S2S_SECRET` is set. Defaults to `127.0.0.1`. The container image sets `0.0.0.0`. |\n| `MCP_HTTP_PORT` | No | HTTP port. Defaults to `8080`. |\n\n`/health` stays unauthenticated and does not read credentials.\n\n### HTTP authentication\n\nWith `MCP_TRANSPORT=http` and a real `CONDUIT_S2S_SECRET`, every `/mcp` request must include `X-Gateway-S2S`. The header value is `t=<unix seconds>,v1=<hex>`, where the hex is HMAC-SHA256 of the literal string `t=<unix seconds>` keyed with `CONDUIT_S2S_SECRET` (64 lowercase hex characters). The timestamp must be within 300 seconds of the server clock. A missing or invalid header is HTTP 401, before vendor credentials are read.\n\n```bash\nTS=$(date +%s)\nSIG=$(printf 't=%s' \"$TS\" | openssl dgst -sha256 -hmac \"$CONDUIT_S2S_SECRET\" -hex | awk '{print $NF}')\ncurl -sS http://127.0.0.1:8080/mcp \\\n  -H \"Content-Type: application/json\" \\\n  -H \"Accept: application/json, text/event-stream\" \\\n  -H \"X-Gateway-S2S: t=${TS},v1=${SIG}\" \\\n  -H \"X-CWA-Server: https://your-server.hostedrmm.com\" \\\n  -H \"X-CWA-Client-ID: your-client-id\" \\\n  -H \"X-CWA-Username: your-username\" \\\n  -H \"X-CWA-Password: your-password\" \\\n  -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools/list\",\"params\":{}}'\n```\n\nIn `AUTH_MODE=gateway`, those `X-CWA-*` headers are the only credential source (`X-CWA-2FA` and `X-CWA-Auth-Method` are optional). A request missing any required header is HTTP 401 and does not use `CW_AUTOMATE_*` from the environment. With `AUTH_MODE=env`, the signed request uses the `CW_AUTOMATE_*` variables instead.\n\n### Docker\n\nThe image listens on `0.0.0.0` inside the container (`MCP_HTTP_HOST`) and defaults to `AUTH_MODE=gateway`. Publish the port on loopback and pass the S2S secret. In gateway mode, Automate credentials arrive on each request as headers; they are not read from the environment.\n\n```bash\ndocker build -t connectwise-automate-mcp .\ndocker run \\\n  -e CONDUIT_S2S_SECRET=your-s2s-secret \\\n  -p 127.0.0.1:8080:8080 \\\n  connectwise-automate-mcp\n```\n\nCompose refuses to start when `CONDUIT_S2S_SECRET` is unset, sets `AUTH_MODE=gateway`, does not inject `CW_AUTOMATE_*`, and publishes `127.0.0.1:8080:8080`:\n\n```bash\nCONDUIT_S2S_SECRET=your-s2s-secret docker compose up\n```\n\nSingle-tenant HTTP (`AUTH_MODE=env`) still requires the S2S secret, then uses `CW_AUTOMATE_*`:\n\n```bash\ndocker run \\\n  -e CONDUIT_S2S_SECRET=your-s2s-secret \\\n  -e AUTH_MODE=env \\\n  -e CW_AUTOMATE_SERVER_URL=https://your-server.hostedrmm.com \\\n  -e CW_AUTOMATE_CLIENT_ID=your-client-id \\\n  -e CW_AUTOMATE_USERNAME=your-username \\\n  -e CW_AUTOMATE_PASSWORD=your-password \\\n  -p 127.0.0.1:8080:8080 \\\n  connectwise-automate-mcp\n```\n\nLocal HTTP without a secret is development-only. It binds `127.0.0.1` only and logs a warning. A non-loopback `MCP_HTTP_HOST` is overridden to `127.0.0.1`:\n\n```bash\nMCP_TRANSPORT=http MCP_ALLOW_INSECURE_DEV=1 node dist/index.js\n```\n\nThe DigitalOcean App Platform template is single-tenant: it sets `AUTH_MODE=env` so the `CW_AUTOMATE_*` secrets stay the credential source, and it declares `CONDUIT_S2S_SECRET`. Set that secret in the App Platform UI or the container exits on boot.\n\n### Authentication methods\n\nThe server supports both ConnectWise Automate authentication methods:\n\n- **`integrator`** (default) – machine-to-machine integrator account. Recommended for automation. Does not use 2FA.\n- **`user`** – interactive user login, which can supply a two-factor code.\n\nYou normally don't need to set `CW_AUTOMATE_AUTH_METHOD`: integrator auth is used by\ndefault, and `user` auth is selected automatically when `CW_AUTOMATE_2FA_CODE` is\nprovided.\n\n## Usage\n\n### As an MCP Server\n\nAdd to your Claude configuration:\n\n```json\n{\n  \"mcpServers\": {\n    \"connectwise-automate\": {\n      \"command\": \"npx\",\n      \"args\": [\"@wyre-ai/connectwise-automate-mcp\"],\n      \"env\": {\n        \"CW_AUTOMATE_SERVER_URL\": \"https://your-server.hostedrmm.com\",\n        \"CW_AUTOMATE_CLIENT_ID\": \"your-client-id\",\n        \"CW_AUTOMATE_USERNAME\": \"your-username\",\n        \"CW_AUTOMATE_PASSWORD\": \"your-password\"\n      }\n    }\n  }\n}\n```\n\n### Navigation\n\nThe server uses a decision tree pattern. Start by navigating to a domain:\n\n1. Use `cwautomate_navigate` to select a domain (computers, clients, alerts, scripts)\n2. Domain-specific tools become available\n3. Use `cwautomate_back` to return to the main menu\n\n### Available Domains\n\n#### Computers\n- List computers with filtering options\n- Get computer details\n- Search computers by name\n- Reboot computers remotely\n- Run scripts on computers\n\n#### Clients\n- List all clients\n- Get client details\n- Create new clients\n- Update existing clients\n\n#### Alerts\n- List alerts with filtering (read-only in the Automate API)\n- Get alert details\n\n#### Scripts\n- List available scripts\n- Get script details\n- Execute scripts on computers\n\n## Development\n\n```bash\n# Install dependencies\nnpm install\n\n# Build\nnpm run build\n\n# Run tests\nnpm test\n\n# Type check\nnpm run typecheck\n\n# Lint\nnpm run lint\n```\n\n## License\n\nApache-2.0\n"}