rocketcyber-mcp
Provides read-only access to the RocketCyber Managed SOC platform, exposing tools to test connectivity, retrieve account information, list monitored agents/endpoints, security incidents, security events, event summaries/statistics, firewall devices, managed apps, Windows Defender status, and Office 365 status, plus resources for account, incidents, and agents.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
rocketcyber-mcp
MCP (Model Context Protocol) server for the RocketCyber Managed SOC platform. Provides read-only access to RocketCyber security data through 10 tools and 3 resources.
Features
10 read-only tools covering all RocketCyber API resources, each annotated
readOnlyHint: trueso MCP clients (e.g. Microsoft 365 Copilot) can skip per-call confirmation prompts3 MCP resources for quick data access
Dual transport: stdio (default) and HTTP Streamable
Lazy SDK initialization on first tool call
Winston logger with all output routed to stderr
Connection test tool for validating credentials
Related MCP server: action1-mcp
One-Click Deployment
Before you click: this server depends on @wyre-ai/node-rocketcyber,
which is hosted on the GitHub Packages npm registry. GitHub Packages has no
anonymous access — even though the package is public, every npm install needs a
token. The cloud builder runs npm install for you, so you must give it one, or
the build fails with npm error 401 Unauthorized ... npm.pkg.github.com.
Create a GitHub Personal Access Token with the
read:packagesscope (classic token). Any GitHub account works — you do not need to be a member of theWYRE-AIorg to read its public packages.Add it as a build variable when prompted by the deploy flow:
Cloudflare Workers → set a build variable named
NODE_AUTH_TOKENto your PAT (Workers → Settings → Build → Variables and Secrets).DigitalOcean App Platform → set an encrypted env var named
GITHUB_TOKENwith scope Build Time to your PAT (the Dockerfile reads it for the install).
Installation
This project depends on @wyre-ai/node-rocketcyber, published to the
GitHub Packages npm registry, which requires a token even for public packages.
Authenticate once, then install:
# Authenticate npm to GitHub Packages (token needs the read:packages scope)
export NODE_AUTH_TOKEN=$(gh auth token) # or a PAT with read:packages
npm install
npm run buildThe repo's .npmrc already points the @wyre-ai scope at GitHub Packages and
reads the token from NODE_AUTH_TOKEN, so no further config is needed.
Configuration
Copy .env.example and set the variables below.
Environment Variable | Required | Default | Description |
| For stdio and | - | RocketCyber API key |
| No |
| API region: |
| No |
| Transport type: |
| No |
|
|
| Yes for HTTP | - | Service-to-service secret. The HTTP server logs an error and exits non-zero when this is empty or a known placeholder ( |
| No | - | Set to exactly |
| No |
| HTTP port (when using http transport) |
| No |
| Bind address when |
| No |
| Log level: |
| No |
| Log format: |
/health stays unauthenticated and does not read credentials. The stdio transport does not use CONDUIT_S2S_SECRET.
HTTP authentication
With MCP_TRANSPORT=http and a real CONDUIT_S2S_SECRET, every /mcp request must include X-Gateway-S2S. The check is verifyS2sHeader in src/mcp/s2s-verify.ts: the header value is t=<unix seconds>,v1=<hex>, where the hex is HMAC-SHA256 of the literal string t=<unix seconds> keyed with CONDUIT_S2S_SECRET (64 lowercase hex characters). The timestamp must be within 300 seconds of the server clock. A missing or invalid header is HTTP 401, before vendor credentials are read.
TS=$(date +%s)
SIG=$(printf 't=%s' "$TS" | openssl dgst -sha256 -hmac "$CONDUIT_S2S_SECRET" -hex | awk '{print $NF}')
curl -sS http://127.0.0.1:8080/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-H "X-Gateway-S2S: t=${TS},v1=${SIG}" \
-H "X-RocketCyber-API-Key: $ROCKETCYBER_API_KEY" \
-H "X-RocketCyber-Region: us" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'In AUTH_MODE=gateway, /mcp also requires X-RocketCyber-API-Key (X-RocketCyber-Region is optional). That header is the only credential source for the request. A missing or blank API key is HTTP 401 and does not fall back to ROCKETCYBER_API_KEY. AUTH_MODE=env still requires the signed X-Gateway-S2S header, then uses ROCKETCYBER_API_KEY from the environment.
Usage
Claude Desktop (stdio)
Add to your Claude Desktop configuration (claude_desktop_config.json):
{
"mcpServers": {
"rocketcyber": {
"command": "node",
"args": ["/path/to/rocketcyber-mcp/dist/entry.js"],
"env": {
"ROCKETCYBER_API_KEY": "your-api-key"
}
}
}
}HTTP Transport
HTTP refuses to start until CONDUIT_S2S_SECRET is a real secret (not a known placeholder). Publish the port on loopback.
# Single-tenant HTTP. Uses ROCKETCYBER_API_KEY after X-Gateway-S2S verifies.
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \
ROCKETCYBER_API_KEY=your-api-key \
MCP_TRANSPORT=http \
npm start
# Local HTTP only, without a service-to-service secret. Always binds 127.0.0.1.
MCP_TRANSPORT=http MCP_ALLOW_INSECURE_DEV=1 npm startDocker
The image listens on 0.0.0.0 inside the container (MCP_HTTP_HOST) and defaults to AUTH_MODE=gateway. Publish the port on loopback and pass a real S2S secret. In gateway mode, RocketCyber credentials arrive on each request as headers; they are not read from the environment.
docker build -t rocketcyber-mcp --build-arg GITHUB_TOKEN="$GITHUB_TOKEN" .
docker run \
-e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \
-p 127.0.0.1:8080:8080 \
rocketcyber-mcpCompose refuses to start when CONDUIT_S2S_SECRET is unset. The gateway service sets AUTH_MODE=gateway, does not inject ROCKETCYBER_API_KEY, and publishes 127.0.0.1:8080:8080:
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" GITHUB_TOKEN="$GITHUB_TOKEN" docker compose upSingle-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses ROCKETCYBER_API_KEY. It is separate from the gateway Compose service above.
docker run \
-e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \
-e AUTH_MODE=env \
-e ROCKETCYBER_API_KEY=your-api-key \
-e ROCKETCYBER_REGION=us \
-p 127.0.0.1:8080:8080 \
rocketcyber-mcpTools
Every tool below only reads data (no tool issues a write to the RocketCyber API), so each is annotated annotations: { readOnlyHint: true } in the tools/list response. MCP clients that honor readOnlyHint — Microsoft 365 Copilot / Copilot Studio among them — use this to skip the per-call confirmation prompt they'd otherwise show before every tool call.
Tool | Description |
|
| Test the connection to RocketCyber API | true |
| Get account information | true |
| List monitored agents/endpoints | true |
| List security incidents | true |
| List security events | true |
| Get event summary/statistics | true |
| List firewall devices | true |
| List managed apps | true |
| Get Windows Defender status | true |
| Get Office 365 status | true |
Resources
URI | Description |
| Account information |
| Security incidents |
| Monitored agents/endpoints |
Development
# Install dependencies
npm install
# Run in development mode
npm run dev
# Build
npm run build
# Start production server
npm startLicense
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Hosted MCP servers for MSP tools: ConnectWise, NinjaOne, Microsoft 365, SentinelOne, Pax8 and more.
MCP server for querying and analyzing data from ad platforms, analytics tools, and spreadsheets
Read-only MCP access to a documented IT fleet: state, changes, posture. 15 tools.
The CustomGPT.ai MCP server is a fully managed, RAG-powered endpoint that connects large language models with private knowledge bases and external data sources. It provides tools for retrieval-augmented generation queries (send_message), data ingestion (upload_file), and source listing, enabling AI agents to query private documents like PDFs with high accuracy and real-time citations.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides secure, read-only access to the TrakSYS manufacturing analytics platform through entity-based tools and guided investigation prompts. It enables users to interact with manufacturing databases and perform data analysis via natural language.MIT
- AlicenseAqualityBmaintenanceAn MCP server for Action1, a cloud-native RMM platform, enabling remote monitoring, patch management, and endpoint management through Action1's API.65Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAn MCP server for Blackpoint Cyber MDR platform, enabling management of security monitoring, threat detection, and incident response through Blackpoint's API.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceMCP server that exposes Acronis Cyber Protect Cloud APIs as 14 read-only tools for managing alerts, tasks, agents, resources, policies, and tenants.-