Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Vulnerability management across all ConnectSecure clients: exposure ranking, CVE impact, blind spots
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
CONNECTSECURE_BASE_URL, CONNECTSECURE_TENANT, CONNECTSECURE_CLIENT_ID, CONNECTSECURE_CLIENT_SECRET, CONNECTSECURE_ACCESS_TOKEN, CONNECTSECURE_USER_ID, CONNECTSECURE_MCP_READ_ONLY, CONNECTSECURE_USER_AGENT, CONNECTSECURE_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILEValues marked secret are keys to your account. Never share them or paste them into a chat.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Fill in the empty values before running it.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
CONNECTSECURE_USER_ID envCONNECTSECURE_MCP_READ_ONLY envCONNECTSECURE_USER_AGENT envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account servosity, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: CONNECTSECURE_BASE_URL, CONNECTSECURE_TENANT, CONNECTSECURE_CLIENT_ID, CONNECTSECURE_CLIENT_SECRET, CONNECTSECURE_ACCESS_TOKEN, CONNECTSECURE_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.4) reached the registry 14 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, HotCodePush
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Unofficial. Community-built Claude Code Skill and MCP server for the ConnectSecure
API. Not affiliated with, endorsed by, or sponsored by ConnectSecure.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Every ConnectSecure API operation, plus a local store that answers vulnerability x asset x client questions across your whole client base 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 ConnectSecure skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register connectsecure-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add connectsecure-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 connectsecure-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs connectsecure-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 ConnectSecure MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every ConnectSecure 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 connectsecure@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the ConnectSecure 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/connectsecure/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/connectsecure/install.ps1 | iex. Then authenticate per the README and runconnectsecure-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/connectsecure/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/connectsecure/install.sh)
The installer drops both connectsecure-cli (the CLI) and connectsecure-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
connectsecure-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/connectsecure/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/connectsecure/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 connectsecure@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/connectsecure --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/connectsecure --force
Hermes speaks MCP natively, so it can also use the connectsecure-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the connectsecure skill from https://github.com/servosity/msp-skills/tree/main/skills/connectsecure. The skill defines how its required CLI (
connectsecure-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.
ConnectSecure hosts each tenant on its own pod, so the CLI needs your pod URL plus the API client credentials from the portal (Settings > Users > (user) > API Key for the client ID and secret; Profile > API Documentation for the pod URL):
export CONNECTSECURE_BASE_URL=https://pod<N>.myconnectsecure.com
export CONNECTSECURE_TENANT= export CONNECTSECURE_CLIENT_ID= export CONNECTSECURE_CLIENT_SECRET= connectsecure-cli doctor
On first use the CLI exchanges those for a short-lived token (POST /w/authorize) and reuses it for at most 30 minutes. If you already hold a token, set CONNECTSECURE_ACCESS_TOKEN and CONNECTSECURE_USER_ID instead of the tenant, client ID and secret.
doctor checks config, paths, and API reachability, and with the tenant, client ID and secret set it mints a token, so a wrong secret shows up as FAIL API: client init error: ConnectSecure rejected the credentials (HTTP 401). It exits 0 even then, so scripts should add --fail-on error. A read command such as connectsecure-cli companies list --limit 1 is the end-to-end check.
exposure, portfolio, blind-spots, suppression-audit and ad-hygiene read a local mirror. Populate it once:
connectsecure-cli sync
A bare sync reads a curated set of 15 resources (companies, assets, agents, vulnerability, remediation, suppression, risk score and Active Directory reports) with GET requests only, and writes them to a SQLite file under your own user account. Credential records, integration secrets and integration-rule params, scheduled jobs (whose rows carry a password field), attack-surface results (whose rows carry creds and hashes fields), custom domains (a precaution: their certificate details are undocumented) and the agent uninstall secret are never written to it; naming one in --resources is refused before any request and stores nothing (sync --resources credentials on its own exits non-zero). Refresh with connectsecure-cli sync --full: a bare re-run only adds and updates rows, so a finding remediated since the last sync stays in the mirror (and in exposure and portfolio) until a --full run prunes it. ConnectSecure's API has no incremental filter, so --full reads the same pages a bare run does. The commands warn when the mirror is older than --max-age (30 minutes by default).
| Question your MSP keeps asking | Command |
|---|---|
| Which open vulnerabilities across every client are most likely to be exploited? | connectsecure-cli exposure --min-epss 0.5 --severity Critical,High |
| What on the CISA Known Exploited list showed up this week? | connectsecure-cli exposure --kev --new-since 7d |
| Which clients carry the most risk, side by side? | connectsecure-cli portfolio --sort max-epss |
| A CVE just made the news. Which clients and assets does it hit, and is there a fix? | connectsecure-cli cve-impact "CVE-2024-3400" |
| Which assets have scan data we cannot trust? | connectsecure-cli blind-spots --stale 14d --agent-stale 48h |
| Which suppressions expired, never expire, or were approved by the person who asked for them? | connectsecure-cli suppression-audit --within 14d |
| Which clients have risky Active Directory accounts or weak password policies? | connectsecure-cli ad-hygiene --stale-logon 90d --min-length 12 |
| What goes in this client's QBR risk slide? | connectsecure-cli qbr "Acme Dental" --since 90d |
| Is my auth and connectivity actually working? | connectsecure-cli doctor |
Full command refer
Only the beginning is shown; read the rest in the repo