Connect Rootly to Conduit

This walkthrough connects Rootly (incident management) to Conduit. You create an API token in Rootly, then add it as an organization connection in Conduit. Rootly is a hosted integration — Conduit talks to Rootly’s own MCP server at mcp.rootly.com, so the only thing you supply is the token.

Menu labels can change

The Rootly steps below reflect the flow at time of writing; menu labels can shift between releases. If a label differs, see Rootly’s API reference overview.

Before you start

You need:

• A Conduit role that can manage connections — owner or admin on your organization.
• A Rootly login that can create API keys under Account > Manage API Keys.

Step 1 — Create an API token in Rootly

1. Sign in to Rootly. Expected: the Rootly dashboard.
2. Go to Account > Manage API Keys and generate a new API key (see Rootly’s API reference for details). Expected: a token value, shown at creation.
3. Copy the token. (Rootly’s own MCP server docs describe what the connected tools can do.)

Caution

Copy the token 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 token, revoke it in Rootly first; the exposed token becomes useless immediately.

Step 2 — Connect Rootly in Conduit

1. In Conduit, go to Connections (/org/catalog). Expected: the vendor catalog.
2. Find Rootly in the catalog (under Security) and click Connect. Expected: a credential form with a single API Token field (placeholder “Generate at Account > Manage API Keys”).
3. Paste the Rootly API token from Step 1 into the API Token field.
4. Click Connect. Expected: Conduit validates the token against Rootly’s hosted MCP server immediately and shows a green Connected status. A bad token 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 Rootly connection. (For per-technician tokens, 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 Rootly tool, such as listing recent incidents. You should get real data back, and the call appears in your audit log with the correct user, vendor (rootly), and a successful status.

Troubleshooting

Symptom	Likely cause
Connect fails with “Invalid Rootly API token. Generate one at Account > Manage API Keys.”	The token is wrong, revoked, or was copied incompletely. Generate a fresh key at Account > Manage API Keys and re-connect.
Connect fails with “Rootly MCP server returned HTTP <status>.”	Rootly’s MCP server answered with a non-auth error — usually a transient vendor-side issue. Wait and retry; if it persists, check Rootly’s status.
Connect fails with “Could not reach Rootly MCP server: <details>”	Conduit couldn’t open a connection to mcp.rootly.com at all — a network issue or a Rootly outage. Retry once connectivity recovers.
Tool calls return 403 “no credentials for vendor”	Rootly isn’t connected at a scope this user can resolve. Connect it at the organization scope, or confirm the user’s team has a token.
Need to rotate the token	Generate a new API key at Account > Manage API Keys in Rootly, then update the credential at /org/catalog. Revoke the old key in Rootly once the new one validates.
Rootly tools don’t show up for an AI client	Reconnect the MCP client so it refetches the tool list, and confirm Rootly shows Connected under Security in Connections.

Related

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