Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
SaaS Alerts alerts, Respond rule triggers and response across every customer tenant.
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.
SAAS_ALERTS_BASE_URL, SAAS_ALERTS_API_KEY, SAAS_ALERTS_USER_AGENT, SAAS_ALERTS_MCP_READ_ONLY, SAAS_ALERTS_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.
SAAS_ALERTS_BASE_URL envSAAS_ALERTS_USER_AGENT envSAAS_ALERTS_MCP_READ_ONLY envPRINTING_PRESS_CLIENT_PROFILE 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 7, 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: SAAS_ALERTS_API_KEY, SAAS_ALERTS_MCP_HTTP_TOKEN
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.3) reached the registry 15 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, Foliosio
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.
Read your support inbox, tag conversations and save draft replies from your AI agent. Never sends.
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 SaaS Alerts
API. Not affiliated with, endorsed by, or sponsored by Kaseya US LLC.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
All four SaaS Alerts APIs (Reports, Manage, Respond and Webhooks) in one CLI and MCP server, plus cross-customer alert triage, the Respond approval queue sorted by deadline, and preview-first account containment. 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 SaaS Alerts skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register saas-alerts-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add saas-alerts-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 saas-alerts-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs saas-alerts-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 SaaS Alerts MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every SaaS Alerts 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 saas-alerts@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the SaaS Alerts 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/saas-alerts/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/saas-alerts/install.ps1 | iex. Then authenticate per the README and runsaas-alerts-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/saas-alerts/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/saas-alerts/install.sh)
The installer drops both saas-alerts-cli (the CLI) and saas-alerts-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
saas-alerts-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/saas-alerts/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/saas-alerts/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 saas-alerts@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/saas-alerts --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/saas-alerts --force
Hermes speaks MCP natively, so it can also use the saas-alerts-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the saas-alerts skill from https://github.com/servosity/msp-skills/tree/main/skills/saas-alerts. The skill defines how its required CLI (
saas-alerts-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.
Set the partner API key from the SaaS Alerts dashboard (Settings > API, GET APIKEY; SaaS Alerts shows the key only until you leave the page, so copy it then):
SAAS_ALERTS_API_KEY=<value> saas-alerts-cli doctor
On Windows (PowerShell):
$env:SAAS_ALERTS_API_KEY = "<value>"
saas-alerts-cli doctor
doctor checks config, paths and API reachability, and sends the key to the Reports API's partner profile endpoint, so a rejected key shows up as a Credentials: invalid row. It exits 0 even then, so scripts should add --fail-on error. The Respond access token is minted on the first Respond call, not by doctor; saas-alerts-cli respond status confirms Respond works end to end.
| Question your MSP keeps asking | Command |
|---|---|
| What fired across every customer in the last 24 hours, critical first? | saas-alerts-cli triage --since 24h --min-severity medium |
| Which Respond triggers expire or auto-ignore soonest? | saas-alerts-cli rule-triggers queue --expiring-within 2h |
| Is one IP address hitting two or more of my customers? | saas-alerts-cli cross-tenant --by ip --since 24h --min-customers 2 |
| Everything on this one account: events, country hops, Respond triggers, devices | saas-alerts-cli investigate "jane.doe@example.com" --since 7d |
| Which customers went silent, lost their Respond connection or have no Respond rules? | saas-alerts-cli coverage --silent 72h |
| Why did SaaS Alerts tickets stop arriving? Is a webhook disabled? | saas-alerts-cli subscriptions health |
| Reject every pending trigger from this noisy rule (preview first) | saas-alerts-cli rule-triggers decide --decision reject --rule --remarks "false positive" |
| Which inbox rules exist at this customer? | saas-alerts-cli reports mailbox-rules --organization-ids |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
Most SaaS Alerts integrations and MCP servers proxy each question into a live API call. That's fine for one record. It dies at scale, when you're asking "which of my 80 customers had a critical alert overnight, and is the same IP behind more than one of them".
This skill syncs customers, events, users and Respond triggers into a local SQLite store, so triage, cross-tenant, investigate and coverage answer across every customer in one local query, and say synced: false instead of an empty all-clear when the data was never synced. It covers all four SaaS Alerts APIs with one partner key: it mints the Respond access token itself (Respond answers "Only secure origins are allowed" to a call that carries only the API key), works the Respond queue by deadline with rule-triggers queue, and previews every change rule-triggers decide and contain would make until you add --confirm.
WYRE-AI's saas-alerts-mcp, which also backs the SaaS Alerts plugin in their msp-claude-plugins marketplace, exposes the SaaS Alerts External Partner API as 30 tools across customers, events, users, devices, billing, scheduled reports and partner settings, with no Respond, suppression or webhook tools; it runs locally with your own key, or through WYRE's hosted Conduit gateway when used from their plugin. This one adds Respond, suppressions and webhooks. It complements the SaaS Alerts dashboard rather than replacing it: the dashboard stays the place to configure monitoring, review alerts and set up R
Only the beginning is shown; read the rest in the repo