Skip to main content
ClaudeWave

MCP server for Kaseya SaaS Alerts — SaaS security monitoring/alerting for M365 & Google Workspace

MCP ServersOfficial Registry0 stars0 forksTypeScriptNOASSERTIONUpdated today
Install in Claude Code / Claude Desktop
Method: Manual
Claude Code CLI
git clone https://github.com/wyre-technology/saas-alerts-mcp
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "saas-alerts-mcp": {
      "command": "node",
      "args": ["/path/to/saas-alerts-mcp/dist/index.js"],
      "env": {
        "SAAS_ALERTS_API_KEY": "<saas_alerts_api_key>"
      }
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
💡 Clone https://github.com/wyre-technology/saas-alerts-mcp and follow its README for install instructions.
Detected environment variables
SAAS_ALERTS_API_KEY
Use cases

MCP Servers overview

# saas-alerts-mcp

Model Context Protocol server for [Kaseya SaaS Alerts](https://saasalerts.com/) — a SaaS security monitoring platform for M365 and Google Workspace events.

Part of the [WYRE Technology MCP fleet](https://github.com/wyre-technology).

## Features

Exposes the full SaaS Alerts External Partner API (v0.20.0) through 30 MCP tools organized by domain:

| Domain | Tools |
|--------|-------|
| **events** | Query/count security events by severity, customer, user, event type; advanced Elasticsearch queries; scroll pagination; recommended actions |
| **customers** | List, get, create, update, delete customers; set IP/country and account whitelists |
| **users** | MSP user info, partner users, customer users |
| **devices** | Unify mapped/unmapped/ignored devices, device organizations |
| **billing** | Billing details by date, billing date history |
| **reports** | List/get/create/delete scheduled reports |
| **partner** | Partner profile, branding settings |

Write/destructive tools require user confirmation via MCP elicitation (fail-open: proceeds if client doesn't support elicitation).

## Authentication

SaaS Alerts uses an API key sent as the `api_key` HTTP header.

Generate your API key in the SaaS Alerts UI under **Settings → API Keys**.

### Local / stdio mode

```bash
export SAAS_ALERTS_API_KEY=your-api-key
node dist/index.js
```

### HTTP mode

```bash
export SAAS_ALERTS_API_KEY=your-api-key
export MCP_TRANSPORT=http
export MCP_HTTP_PORT=8080
node dist/http.js
```

### WYRE Gateway mode

When running behind the WYRE MCP Gateway, set `AUTH_MODE=gateway`. The gateway injects the API key per-request via the `X-SaaS-Alerts-API-Key` header — no env var needed.

## Running with Docker

```bash
docker compose up
```

Or pull from GHCR:

```bash
docker run -e SAAS_ALERTS_API_KEY=your-key \
  -e MCP_TRANSPORT=http \
  -p 8080:8080 \
  ghcr.io/wyre-technology/saas-alerts-mcp:latest
```

## Development

```bash
npm install
npm run build
npm test
npm run lint
node scripts/lint-destructive-warnings.mjs src
```

## Destructive tool confirmation

Tools that permanently delete data (customer delete, scheduled report delete) carry:
- `⚠ DESTRUCTIVE — IRREVERSIBLE` description prefix
- `annotations.destructiveHint: true`
- Elicitation confirmation guard (additive — proceeds if client doesn't support elicitation)

Always confirm with the user before invoking these tools.

## License

Apache-2.0 — see [LICENSE](LICENSE).

What people ask about saas-alerts-mcp

What is wyre-technology/saas-alerts-mcp?

+

wyre-technology/saas-alerts-mcp is mcp servers for the Claude AI ecosystem. MCP server for Kaseya SaaS Alerts — SaaS security monitoring/alerting for M365 & Google Workspace It has 0 GitHub stars and was last updated today.

How do I install saas-alerts-mcp?

+

You can install saas-alerts-mcp by cloning the repository (https://github.com/wyre-technology/saas-alerts-mcp) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is wyre-technology/saas-alerts-mcp safe to use?

+

wyre-technology/saas-alerts-mcp has not been audited yet by our security agent. Review the original repository on GitHub before using it in production.

Who maintains wyre-technology/saas-alerts-mcp?

+

wyre-technology/saas-alerts-mcp is maintained by wyre-technology. The last recorded GitHub activity is from today, with 1 open issues.

Are there alternatives to saas-alerts-mcp?

+

Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.

Deploy saas-alerts-mcp to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: wyre-technology/saas-alerts-mcp
[![Featured on ClaudeWave](https://claudewave.com/api/badge/wyre-technology-saas-alerts-mcp)](https://claudewave.com/repo/wyre-technology-saas-alerts-mcp)
<a href="https://claudewave.com/repo/wyre-technology-saas-alerts-mcp"><img src="https://claudewave.com/api/badge/wyre-technology-saas-alerts-mcp" alt="Featured on ClaudeWave: wyre-technology/saas-alerts-mcp" width="320" height="64" /></a>

More MCP Servers

saas-alerts-mcp alternatives