SaaS Alerts MCP Server

An MCP server for the SaaS Alerts partner API. SaaS Alerts monitors an MSP's customers' Microsoft 365, Google Workspace, Salesforce and Dropbox tenants and raises security events (failed and foreign logins, external file sharing, OAuth grants, admin changes). This server lets an AI agent query and count those events, run Elasticsearch searches over them, list customers, users, devices, billing and scheduled reports and, on explicit request, manage customers, whitelists, scheduled reports and report branding.

• Transport: MCP Streamable HTTP at POST /mcp, health probe at GET /health

• Stateless and multi-tenant: the API key arrives on every request as an HTTP header and is never stored; every tool is listed from the first tools/list

• Python 3.12, uv, FastMCP, httpx

• License: Apache-2.0, Copyright 2026 MSPbots.ai

MSPbots Connector

The MCP Gateway built for MSPs: visible, controlled, and your data stays where it belongs.

Get started at connect.mspbots.ai →

MSPbots Connector gives your AI clients one MCP URL to reach your entire MSP stack (RMM, PSA, documentation, security, finance), and gives you control over who can call which tool and a record of everything that was called.

Hosted service: connect.mspbots.ai · Free to use.

Why Connector

Quick start

1. Sign up at connect.mspbots.ai.

2. Connect your vendors. Pick from 150+ connectors and authorize each one on the vendor's own page, or bring your own API keys. No extra vendor accounts needed.

3. Set access. Create roles and decide which tools each role may call. Nothing is allowed until you allow it.

4. Add your MCP URL to your AI client. Copy the URL from your Connector dashboard into Claude, ChatGPT, Cursor, VS Code, Gemini, Codex, or any MCP-capable client.

5. Ask your AI to do real work, and watch every call appear in the audit log.

Features

Unified gateway

• One MCP URL for all your AI clients

• 150+ connectors across the MSP stack

• Custom MCP servers supported, free

• Authorization happens on each vendor's own page; the AI never sees passwords or tokens

• Bring your own credentials: use the vendor API keys you already have

• Multiple accounts per app; connect once, reuse across AI clients

• Tool search: finds the right action for the task

• One sign-in; vendor credentials are injected behind the scenes and OAuth tokens refresh automatically

Visibility

• Audit log for every tool call (who, which vendor, when)

• Usage dashboard: call volume, top vendors, error rate, per-user activity

• Export audit logs to CSV, or stream to Loki, Graylog, or LogScale (SIEM)

• Optional recording of tool arguments and result summaries (off by default, enabled per organization)

Control

• Per-role, per-tool allowlist, deny by default

• owner / admin / member roles

• SCIM provisioning with Entra ID, Okta, JumpCloud, and Google Workspace

Security

• Credentials encrypted one record at a time (AES-256-GCM, per-record key)

• AI clients authenticate with OAuth 2.1 + PKCE

• Vendor responses are scanned for prompt-injection patterns and returned as structured data. This is one layer of defense, not a guarantee against every attack.

• Static egress IP for customer firewall and API allowlisting

Pricing

Free.

Links: connect.mspbots.ai · mspbots.ai

Related MCP server: proofpoint-essentials-mcp

Authentication headers

Where to get it: a SaaS Alerts partner administrator generates an API key in the SaaS Alerts partner portal. The key acts on the whole partner account (all customers).

How the key is sent to SaaS Alerts: in the api_key header of every call to https://us-central1-the-byway-248217.cloudfunctions.net/reportApi/api/v1/..., the API address published in the SaaS Alerts API reference.

A request to /mcp without the key gets HTTP 401.

Tools

All tools return a JSON string. Event tools return triage fields only (time, type, severity, description, user, customer, product, IP, location) unless verbose: true is passed.

Paging: saas_alerts_events_query returns {events, count, has_more, next_from} (also with verbose); pass next_from as from to continue; the API gives no total, use saas_alerts_events_count. Lists the API returns in full (customers, partner and customer users, scheduled reports, device organizations and the mapped / unmapped / ignored devices, recommended actions) take offset / limit and return next_offset. When a result is cut to fit the 20,000-character limit, next_from / next_offset start right after the last record returned. Elasticsearch results (events_query_advanced, events_scroll) that are cut leave out _scroll_id, which would skip the rest: run the search again with a smaller size. saas_alerts_recommended_actions returns one record per event type; pass event_type for one.

start_date / end_date take ISO 8601 or epoch milliseconds and are sent as ISO 8601 UTC. Body objects are checked against the fields the API documents; an unknown field is rejected with invalid_argument before anything is sent.

Errors come back as a JSON envelope instead of an exception:

{"error": {"code": "unauthorized", "message": "SaaS Alerts returned HTTP 401 for customers: Unauthorized", "retryable": false}}

code is one of not_configured, unauthorized, not_found, invalid_argument, rate_limited, upstream_error. Reads are retried with backoff on 429, 5xx and network errors; writes are retried only on 429.

Run locally

uv sync
uv run python -m saas_alerts_mcp          # listens on 0.0.0.0:8080

or with Docker:

docker build --platform linux/amd64 -t saas-alerts-mcp:dev .
docker run --rm -p 8080:8080 saas-alerts-mcp:dev

Configuration (environment variables, all optional): MCP_HTTP_HOST (default 0.0.0.0), MCP_HTTP_PORT (default 8080), LOG_LEVEL (default INFO). The key is never read from the environment.

Testing example

# list tools
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-SaaS-Alerts-API-Key: your-saas-alerts-api-key" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

# critical events of the last day
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-SaaS-Alerts-API-Key: your-saas-alerts-api-key" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"saas_alerts_events_query","arguments":{"alert_status":"critical","start_date":"2026-01-01T00:00:00Z","size":20}}}'

Unit tests (no network access needed):

uv run pytest

Delivery notes

• Tool count (30). Kept as is because the tool names are an existing contract.

• API contract. Requests follow the SaaS Alerts API reference (version 3.362.0). Event filters map to the API's customerId, alertStatus, repeated eventType, userEmail, start / end, from, size and timeSort query parameters.

• Elasticsearch tools. query is the search body itself (the API wraps it as body). saas_alerts_events_query_advanced accepts an optional scroll lifetime so the response carries a _scroll_id for saas_alerts_events_scroll, which sends the API's required scroll lifetime (default 1m).

• Devices. The API requires a confidence value for unmapped devices; it defaults to 0 (all suggestions). The former only_with_suggestions flag had no API parameter and was removed.

• Billing. billing_date is sent as the billingDate query parameter, which the API reference does not list; use a value returned by saas_alerts_billing_list_dates.

• Writes. Whitelist and branding tools replace the current settings and are annotated as destructive. Deletes need confirm: true.

License

Apache License 2.0 - see LICENSE and NOTICE.