RocketCyber MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@RocketCyber MCP Servershow me the latest confirmed RocketCyber incidents from this week"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
RocketCyber MCP Server
An MCP server for the RocketCyber customer API (v3). RocketCyber is a managed SOC for MSPs: agents on endpoints and firewall log collectors feed detection apps, and threats the SOC confirms become incidents. This server lets an AI agent read incidents, app events and event summaries, the agent and firewall inventory, the detection apps, the account hierarchy, and Microsoft Defender and Microsoft 365 status. Every tool is read-only.
Transport: MCP Streamable HTTP at
POST /mcp, health probe atGET /healthStateless 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/listPython 3.12, uv, FastMCP, httpx
License: Apache-2.0, Copyright 2026 MSPbots.ai
Authentication headers
Header | Required | Type | Default | Allowed values | Description | Example |
| Yes | string | none | - | RocketCyber customer API access token |
|
| No | string |
|
| Data region of the RocketCyber account |
|
Where to get it: in the RocketCyber console, an administrator copies the customer API access token from the provider account's settings (the API reference links to the step-by-step help article). The token reads every customer account under that provider account.
How the key is sent to RocketCyber: as Authorization: Bearer <token> on every call to
https://api-us.rocketcyber.com/v3/... (region us) or https://api-eu.rocketcyber.com/v3/...
(region eu).
A request to /mcp without the key gets HTTP 401; a region other than us / eu gets HTTP 400.
Related MCP server: Auvik MCP Server
Tools
All tools return a JSON string. Paged lists keep the API's {totalCount, currentPage, totalPages, dataCount, data} and add summary {count, total, page, total_pages, has_more, next_page}.
accountId scopes a tool to one customer account; without it the tool covers every account the
token can see. dates filters take start|end (ISO dates, either side may be empty; a single date
means "from that date on"). sort takes field, field:asc or field:desc. pageSize defaults
to 25 (the API's own default is 1000), max 1000.
Tool | Purpose | Parameters (required in bold) |
| Check the token works in the selected region | - |
| Account details and child customer account ids | accountId |
| Confirmed incidents, newest first; description / remediation trimmed to ~300 characters unless | page, pageSize, sort, accountId, status, dates (created), title ( |
| Events (detections) of one detection app | appId, page, pageSize, sort, accountId, severity ( |
| Event counts per detection app | accountId, dates |
| Endpoint agents with OS, IP, version and online state | page, pageSize, sort, accountId, connectivity ( |
| Firewalls sending logs, with log counters | page, pageSize, sort, accountId, vendor, ipAddress, macAddress |
| Detection apps (ids and descriptions) | sort ( |
| Microsoft Defender status | accountId |
| Microsoft 365 security status (Secure Score trend) | accountId |
Errors come back as a JSON envelope instead of an exception:
{"error": {"code": "unauthorized", "message": "RocketCyber returned HTTP 401 for account: Authentication failed. Please provide valid credentials.", "retryable": false}}code is one of not_configured, unauthorized, not_found, invalid_argument,
rate_limited, upstream_error. Calls are retried with backoff on 429 (honouring Retry-After),
5xx and network errors.
Run locally
uv sync
uv run python -m rocketcyber_mcp # listens on 0.0.0.0:8080or with Docker:
docker build --platform linux/amd64 -t rocketcyber-mcp:dev .
docker run --rm -p 8080:8080 rocketcyber-mcp:devConfiguration (environment variables, all optional): MCP_HTTP_HOST (default 0.0.0.0),
MCP_HTTP_PORT (default 8080), LOG_LEVEL (default INFO). The token 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-Rocketcyber-Api-Key: your-api-key" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
# open incidents created this year
curl -s http://localhost:8080/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "X-Rocketcyber-Api-Key: your-api-key" \
-H "X-Rocketcyber-Region: us" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"rocketcyber_list_incidents","arguments":{"status":"open","dates":"2026-01-01|"}}}'Unit tests (no network access needed):
uv run pytestDelivery notes
Tool count (10). Kept as is because the tool names and camelCase parameter names are an existing contract.
API contract. Requests follow RocketCyber's published customer API reference (
https://api-doc.rocketcyber.com, v3). Older versions passed some filters through under names the API does not have; they now map to the documented query parameters: agentsplatform->os, agentsdates->created, incidentsdates->createdAt, eventsseverity->verdict, firewallsvendor->type, appssort->sort+order.Removed parameters with no API filter: incidents
severity; eventseventTypeandhostname(usedeviceIdordetailsinstead); firewallsconnectivityandhostname; appspageandpageSize(the apps endpoint is not paged). Appsnamefilters the returned list locally.Event summary.
datesis passed through as in earlier versions; the API reference lists onlyaccountIdfor this endpoint.
License
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only discovery of AI agents in your Communicate workspace.
Read-only finance and operations controls for AI agents with evidence and safe next actions.
Read-only access to an ET Ducky organization's agents, alerts, and fleet summary
Read-only CVE intelligence, remediation playbooks, and agent setup guides. Not a scanner.
Related MCP Servers
- AlicenseAqualityBmaintenanceProvides read-only visibility into CyberQP privileged access management data, including customer and account metadata, tenant event logs, and Just-In-Time account status and policies, for AI assistants.10Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query an MSP's network monitoring data — tenants, discovered devices, networks, interfaces, configuration backups, alerts, performance statistics and billing usage — through multi-tenant, stateless Streamable HTTP with credentials supplied per request. Read-only by default, with optional alert dismissal and raw API access for changes.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read-only query an MSP's Action1 data — organizations, managed endpoints, missing OS and third-party updates, and scheduled automations — using per-request credentials that are never stored. Supports multi-tenant, stateless access over Streamable HTTP with paginated list results and structured error responses.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read Datto SIRIS and ALTO backup appliance data, including protected machines and shares, snapshot history with local and screenshot verification, offsite replication status, fleet alerts, and partner portal activity logs. Provides read-only access to the Datto partner REST API with stateless, per-request authentication.Apache 2.0