Connect RocketCyber to Conduit

This walkthrough connects RocketCyber (managed SOC / security) to Conduit. You obtain an API access token from RocketCyber, then add it as an organization connection in Conduit. Once connected, any MCP client your organization uses can call RocketCyber tools through Conduit’s gateway.

Menu labels can change

The RocketCyber steps below reflect the Kaseya/RocketCyber flow at time of writing; menu labels can shift between releases. If a label differs, follow RocketCyber’s guide to finding your API access token.

Before you start

You need:

• A Conduit role that can manage connections — owner or admin on your organization.
• A RocketCyber login with access to the account’s API settings.
• To know which region your RocketCyber tenant runs in. RocketCyber operates separate US and EU platforms — check the address bar when you’re signed in to your RocketCyber console. An API key only works against the region it was issued in.

Step 1 — Get your RocketCyber API key

1. Sign in to your RocketCyber console. Expected: the RocketCyber dashboard.
2. Locate or generate your API access token following RocketCyber’s guide. Expected: a token value you can copy.
3. Copy the token. (The RocketCyber API reference describes what the token can do.)

Caution

Copy the key now and store it somewhere safe. Don’t paste it into chat, email, or a shared document — the next step moves it directly into Conduit, which encrypts it at rest. If you accidentally expose the key, regenerate it in RocketCyber first; the exposed key becomes useless immediately.

Step 2 — Connect RocketCyber in Conduit

1. In Conduit, go to Connections (/org/catalog). Expected: the vendor catalog.
2. Find RocketCyber in the catalog (under Security) and click Connect. Expected: a credential form with two fields.
3. Fill the fields:
   • API Key (required) — paste the token from Step 1.
   • Region (optional) — a dropdown with two options, us and eu. Pick the region your RocketCyber console runs in. If you leave it unset, Conduit defaults to US. Picking the wrong region makes validation fail even when the key itself is correct.
4. Click Connect. Expected: Conduit validates the key against the regional RocketCyber API immediately and shows a green Connected status. A bad key or wrong region is rejected here, not on the first tool call.

The credential is stored at the organization scope, so every technician in your org shares this RocketCyber connection. (For per-technician keys, connect at the personal scope instead — see Vendor connections.)

Verify it worked

Connect an MCP client to Conduit — Claude Desktop, Claude Code, Cursor, or any MCP-compatible client (see Connecting an AI client) — and ask it to run a read-only RocketCyber tool, such as listing incidents or agents. You should get real data back, and the call appears in your audit log with the correct user, vendor (rocketcyber), and a successful status.

Troubleshooting

Symptom	Likely cause
Connect fails with “Invalid RocketCyber API key or wrong region.”	Either the token is wrong/revoked, or the Region selection doesn’t match where your tenant lives. Check the address bar of your RocketCyber console, set us or eu to match, and re-check the token.
Connect fails with “RocketCyber returned HTTP <status>.”	RocketCyber answered with a non-auth error — usually a transient vendor-side issue or maintenance window. Wait and retry; if it persists, check RocketCyber’s status.
Tool calls return 403 “no credentials for vendor”	RocketCyber isn’t connected at a scope this user can resolve. Connect it at the organization scope, or confirm the user’s team has a key.
Vendor health shows yellow/degraded	Conduit’s health check sees RocketCyber responding slowly. Usually a transient vendor-side load spike — recovers automatically.
Need to rotate the key	Generate a new API access token in RocketCyber, then update the credential at /org/catalog.

Related

• Vendor connections — credential scopes, rotation, and the full vendor catalog.
• Security — how Conduit encrypts and resolves the credential you just stored.