SaaS Alerts MCP Server
by wyre-technologyio.github.wyre-technology/saas-alerts-mcpv1.2.4
MCP server for Kaseya SaaS Alerts — SaaS security monitoring for M365 & Google Workspace.
context tax
queued
security
queued
cold start
queued
freshness
Active4d ago
Install SaaS Alerts MCP server
Install in Claude Code
claude mcp add saas-alerts-wyre-technology -e SAAS_ALERTS_API_KEY='<saas-alerts-api-key>' -- docker run -i --rm -e SAAS_ALERTS_API_KEY ghcr.io/wyre-technology/saas-alerts-mcp:v1.2.4Install in Cursor
{
"mcpServers": {
"saas-alerts-wyre-technology": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SAAS_ALERTS_API_KEY",
"ghcr.io/wyre-technology/saas-alerts-mcp:v1.2.4"
],
"env": {
"SAAS_ALERTS_API_KEY": "<saas-alerts-api-key>"
}
}
}
}Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).
Install in Claude Desktop
{
"mcpServers": {
"saas-alerts-wyre-technology": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SAAS_ALERTS_API_KEY",
"ghcr.io/wyre-technology/saas-alerts-mcp:v1.2.4"
],
"env": {
"SAAS_ALERTS_API_KEY": "<saas-alerts-api-key>"
}
}
}
}Settings → Developer → Edit Config (claude_desktop_config.json), then restart.
Install in VS Code
{
"servers": {
"saas-alerts-wyre-technology": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SAAS_ALERTS_API_KEY",
"ghcr.io/wyre-technology/saas-alerts-mcp:v1.2.4"
],
"env": {
"SAAS_ALERTS_API_KEY": "<saas-alerts-api-key>"
}
}
}
}Add to .vscode/mcp.json in your workspace.
Install in Windsurf
{
"mcpServers": {
"saas-alerts-wyre-technology": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SAAS_ALERTS_API_KEY",
"ghcr.io/wyre-technology/saas-alerts-mcp:v1.2.4"
],
"env": {
"SAAS_ALERTS_API_KEY": "<saas-alerts-api-key>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json.
Configuration
| Variable | Required | Secret | Description |
|---|---|---|---|
| SAAS_ALERTS_API_KEY | yes | yes | SaaS Alerts API key (sent as the api_key header). Required. |
| MCP_TRANSPORT | — | — | Transport mode. 'stdio' for local CLI; image defaults to 'http' for gateway hosting. |
| AUTH_MODE | — | — | 'env' reads vars locally; 'gateway' expects header injection from the WYRE MCP Gateway. |
| LOG_LEVEL | — | — | Log verbosity: debug, info, warn, error |
Freshness
Active — last maintenance signal 4d ago. The newest of the signals below sets the band.
Last commit (default branch)
2026-10-05 · 4d ago · GitHub
Latest release
2026-09-25 · 15d ago · GitHub · v1.2.8
Package published
no data · npm/PyPI
Registry entry updated
2026-08-21 · 50d ago · official registry · v1.2.4
FAQ
›How do I install the SaaS Alerts MCP server in Claude Code?
Run: claude mcp add saas-alerts-wyre-technology -e SAAS_ALERTS_API_KEY='<saas-alerts-api-key>' -- docker run -i --rm -e SAAS_ALERTS_API_KEY ghcr.io/wyre-technology/saas-alerts-mcp:v1.2.4. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.
›Does SaaS Alerts require an API key?
Yes. It expects SAAS_ALERTS_API_KEY, of which 1 is a secret.
›Can I use SaaS Alerts as a remote (hosted) MCP server?
No hosted endpoint is published; it runs locally over stdio.
›Is SaaS Alerts in the official MCP registry?
Yes, as io.github.wyre-technology/saas-alerts-mcp.
Alternatives to SaaS Alerts
Other monitoring & observability MCP servers.