ConnectSecure MCP

ConnectSecure + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP

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.

Works with your agent

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):

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.

Also for the Microsoft and Google stacks

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.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly *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.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Download 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

Path A - paste one prompt into your AI agent (recommended)

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, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/connectsecure/install.ps1 | iex. Then authenticate per the README and run connectsecure-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

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

Upgrade to the latest 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.

Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, or another MCP client

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.

Install for Hermes

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.

Install for OpenClaw

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 the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

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.

Sync before you ask

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).

What this skill does

Full command refer