Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
ConnectWise RMM (Asio) MCP: offline agents, patch posture, and script runs across every client.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
CONNECTWISE_RMM_CLIENT_ID, CONNECTWISE_RMM_CLIENT_SECRET, CONNECTWISE_RMM_OAUTH_SCOPE, CONNECTWISE_RMM_BASE_URL, CONNECTWISE_RMM_TOKEN_URL, CONNECTWISE_RMM_USER_AGENT, CONNECTWISE_RMM_MCP_READ_ONLY, CONNECTWISE_RMM_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
링크는 제작자의 파일로 바로 연결돼요. 우리가 보관하거나 다시 패키징하지 않아요. 파일을 열면 Claude Desktop이 설치해요.
터미널에서 이 명령어를 실행하세요
실행하기 전에 빈 값을 채워 주세요.
브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
CONNECTWISE_RMM_OAUTH_SCOPE envCONNECTWISE_RMM_BASE_URL envCONNECTWISE_RMM_TOKEN_URL envCONNECTWISE_RMM_USER_AGENT envCONNECTWISE_RMM_MCP_READ_ONLY env이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검
레지스트리 이름이 GitHub 계정 servosity 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: CONNECTWISE_RMM_CLIENT_ID, CONNECTWISE_RMM_CLIENT_SECRET, CONNECTWISE_RMM_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.1.3)은 15일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 MCPB도 있어야 해요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, OpenTakeoff
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Construction takeoff for AI agents: load plans, set scale, measure, count, export with provenance.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Unofficial. Community-built Claude Code Skill and MCP server for the ConnectWise RMM
(Asio) partner API. Not affiliated with, endorsed by, or sponsored by ConnectWise, LLC.
Full skill page - install, outcomes, safety model.
66 ConnectWise RMM (Asio) partner API operations, plus a local fleet database, patch-compliance rollups, and script runs you can preview, schedule and watch in one command. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.
Security note (until this connector is reprinted). Do not run HTTP mode
(
--transport http), not even on localhost. This build checks a token, but it
predates the fix release's request size and time limits. The MCP tools can
also make changes with your credentials. Use the default stdio transport. If
you set up a tunnel for a remote agent, shut it down. A fix is on the way.
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the ConnectWise RMM skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register connectwise-rmm-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add connectwise-rmm-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet. |
| Codex CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste the install prompt below. |
| GitHub Copilot (VS Code) | Run installer, add connectwise-rmm-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs connectwise-rmm-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server, and this connector's HTTP mode is paused until it is reprinted (see the security note in mcp-install.md), so msp-skills does not support it yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.
Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list. |
| Google Gemini | Gemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills yet. |
Skill-native agents (also covered): Hermes and OpenClaw read this skill's
SKILL.mddirectly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).
Run more than one agent? Install across all 51+ supported agents in one command:
npx skills add Servosity/msp-skills@latest(requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.
.mcpbDownload ConnectWise RMM MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every ConnectWise RMM release on the releases page.)
Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:
/plugin marketplace add Servosity/msp-skills
/plugin install connectwise-rmm@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the ConnectWise RMM Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/connectwise-rmm/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/connectwise-rmm/install.ps1 | iex. Then authenticate per the README and runconnectwise-rmm-cli --helpto explore.
The same prompt works in any agent that can run shell.
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/connectwise-rmm/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/connectwise-rmm/install.sh)
The installer drops both connectwise-rmm-cli (the CLI) and connectwise-rmm-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
connectwise-rmm-cli --version
The installer always fetches the current release - re-run it to upgrade:
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/connectwise-rmm/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/connectwise-rmm/install.ps1 | iex
Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update connectwise-rmm@msp-skills.
After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.
From the Hermes CLI:
hermes skills install servosity/msp-skills/skills/connectwise-rmm --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/connectwise-rmm --force
Hermes speaks MCP natively, so it can also use the connectwise-rmm-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the connectwise-rmm skill from https://github.com/servosity/msp-skills/tree/main/skills/connectwise-rmm. The skill defines how its required CLI (
connectwise-rmm-cli) can be installed via theopenclaw:frontmatter block.
OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.
Create an API client under Integrations > API Access in the ConnectWise portal, then set its ID and secret:
CONNECTWISE_RMM_CLIENT_ID=<value> CONNECTWISE_RMM_CLIENT_SECRET=<value> connectwise-rmm-cli doctor
A client ID starting 0e30, 0e31 or 0e32 picks North America, Europe or Australia for you; if yours starts differently, set CONNECTWISE_RMM_BASE_URL to your region's API host. If your key was not granted every scope this connector uses, run connectwise-rmm-cli scopes --agent and set the CONNECTWISE_RMM_OAUTH_SCOPE line it prints - ConnectWise rejects a whole token request that asks for one scope the key lacks. Then pull the fleet into the local mirror:
connectwise-rmm-cli sync --resources companies,sites,endpoints,tickets
doctor mints a token from your client ID and secret and verifies it against the API, so a wrong secret, a missing scope or a wrong host shows up as a failed Credentials line. It exits 0 even when a check fails, so scripts should add --fail-on error.
| Question your MSP keeps asking | Command |
|---|---|
| Which endpoints are offline or silent for more than a day, by client? | connectwise-rmm-cli fleet stale --older-than 24h --agent |
| Which clients are behind on patches, worst first? | connectwise-rmm-cli fleet patch-posture --min-compliance 90 --agent |
| Which machines need a reboot this patch week, and who is logged on? | connectwise-rmm-cli fleet reboot-due --agent |
| Which machine is this user logged on to? | connectwise-rmm-cli fleet whois "jsmith" --agent |
| Give me one client's health card for the review. | connectwise-rmm-cli fleet scorecard "Acme Corp" --agent |
| Why did last night's script fail, and on which machines? | connectwise-rmm-cli fleet task-failures " " --agent |
Run a script on endpoints - preview first, then schedule with --confirm. | connectwise-rmm-cli run --script "Restart Print Spooler" --endpoint " " |
| Which OAuth scopes did my API key actually get? | connectwise-rmm-cli scopes --agent |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
Most ConnectWise RMM integrations and MCP servers - the open-source connectwise-asio-mcp and asio-cli among them - work against the live API with no persistent local copy. That's fine for one device. It dies at scale, when you're asking "which agents are offline across all 40 clients" or "who's behind on patches before this morning's client review", because Asio returns per-endpoint rows keyed by IDs, never a per-client roll-up, and caps availability checks at 400 endpoints per call.
This skill syncs ConnectWise RMM into a local SQLite mirror with full-text search, batches the live availability checks, and caches patch summaries. Aggregate questions become one local join, and the AI sees the answer, not the raw data. Compound commands like fleet patch-posture, fleet scorecard, and fleet task-failures join companies, sites, endpoints, patch summaries, tickets and task results - work a stateless API wrapper can't do.
ConnectWise RMM (the cloud RMM on the ConnectWise Asio platform, formerly Command and Continuum) is built around a per-client, per-device view, and its partner API is the same shape: ConnectWise's own docume
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요