Rootly

Rootly MCP Server

An MCP server for the Rootly API for Cursor, Windsurf, Claude, and other MCP clients.

Quick Start

Use the hosted MCP server. No local installation required.

Hosted Transport Options

• Streamable HTTP (recommended): https://mcp.rootly.com/mcp
• Code Mode: https://mcp.rootly.com/mcp-codemode
• SSE (deprecated, removed after 2026-11-20): https://mcp.rootly.com/sse

[!WARNING]

SSE is deprecated. The hosted https://mcp.rootly.com/sse endpoint and the self-hosted --transport sse option will be removed after 2026-11-20. Switch your client to Streamable HTTP (https://mcp.rootly.com/mcp) or Code Mode (https://mcp.rootly.com/mcp-codemode); for most clients that means changing the URL and, if your client config has one, setting the transport to http/streamable-http. SSE responses now carry Deprecation, Sunset and Link: rel="successor-version" headers.

Toolsets

Every client loads the whole tool list into the model's context: the full surface is about 125k tokens. Tools are grouped into toolsets (the same model as GitHub's and Datadog's MCP servers) so a client can load only what it needs. Recommended: `?toolsets=core`, about 29 tools and 10k tokens. Without a selection you still get every tool, so existing configurations keep working.

• Pick toolsets: https://mcp.rootly.com/mcp?toolsets=core,workflows, or send X-MCP-Toolsets: core,workflows
• Actions that run later are separate: workflow_tasks and automations set up things Rootly does on its own afterwards (workflow steps, AI automations). Leave them out to let an assistant read and use workflows and AI investigations without being able to set those up
• Everything: ?toolsets=all (about 280 tools)
• Read-only: add readonly=true (or X-MCP-Readonly: true), e.g. ?toolsets=all&readonly=true. Any value other than false/0/no/off turns it on. Write tools are hidden and refused, and the server also refuses any non-GET request to the Rootly API on that connection. It is a per-connection guard; for a hard guarantee, connect with a Rootly API key whose role cannot write
• Deprecated: `?tool_profile=` and `X-Rootly-Tool-Profile`. They still work (full/all mean ?toolsets=all; slim keeps its fixed ~85-tool list) and will be removed; switch to ?toolsets=. Each use is logged so remaining clients can be found
• Server-wide default: ROOTLY_MCP_TOOLSETS=core,alerts sets what a client gets with no selection (default all); ROOTLY_MCP_HOSTED_TOOL_PROFILE=slim makes slim the default instead
• Exact custom override: ROOTLY_MCP_ENABLED_TOOLS=... replaces toolsets entirely

A tool outside the selection is refused with the toolset that holds it (list_workflows is not available here: it is in the 'workflows' toolset ... Reconnect with ?toolsets=core,workflows), and the server instructions list every toolset, so an assistant can tell you the exact change. Code Mode (/mcp-codemode) always has the full catalog; readonly=true applies there too, to every tool a script calls. readonly also applies under the slim profile and ROOTLY_MCP_ENABLED_TOOLS.

General Remote Setup

With OAuth2 (recommended):

{

"mcpServers": { "rootly": { "url": "https://mcp.rootly.com/mcp" } } }

Your MCP client handles OAuth2 login automatically — a browser window opens for you to authenticate with Rootly. No API token needed.

With API Token:

{

"mcpServers": { "rootly": { "url": "https://mcp.rootly.com/mcp", "headers": { "Authorization": "Bearer YOUR_ROOTLY_API_TOKEN" } } } }

Code Mode:

{

"mcpServers": { "rootly": { "url": "https://mcp.rootly.com/mcp-codemode" } } }

If your config still points at https://mcp.rootly.com/sse, replace it with https://mcp.rootly.com/mcp before 2026-11-20 (SSE is deprecated, see above).

Agent Setup

Claude Code

With OAuth2 (recommended):

claude mcp add --transport http rootly https://mcp.rootly.com/mcp

Code Mode:

claude mcp add --transport http rootly-codemode https://mcp.rootly.com/mcp-codemode

With API Token:

claude mcp add --transport http rootly https://mcp.rootly.com/mcp \

--header "Authorization: Bearer YOUR_ROOTLY_API_TOKEN"

Manual Configuration — Create .mcp.json in your project root:

{

"mcpServers": { "rootly": { "type": "http", "url": "https://mcp.rootly.com/mcp" } } }

Gemini CLI

Install the extension:

gemini extensions install https://github.com/rootlyhq/rootly-mcp-server

Or configure manually in ~/.gemini/settings.json:

{

"mcpServers": { "rootly": { "command": "uvx", "args": ["--from", "rootly-mcp-server", "rootly-mcp-server"], "env": { "ROOTLY_API_TOKEN": " " } } } }

Cursor

Add to .cursor/mcp.json or ~/.cursor/mcp.json:

With OAuth2 (recommended):

{

"mcpServers": { "rootly": { "url": "https://mcp.rootly.com/mcp" } } }

With API Token:

{

"mcpServers": { "rootly": { "url": "https://mcp.rootly.com/mcp", "headers": { "Authorization": "Bearer " } } } }

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

With OAuth2 (recommended):

{

"mcpServers": { "rootly": { "serverUrl": "https://mcp.rootly.com/mcp" } } }

With API Token:

{

"mcpServers": { "rootly": { "serverUrl": "https://mcp.rootly.com/mcp", "headers": { "Authorization": "Bearer " } } } }

Codex

Add to ~/.codex/config.toml:

With OAuth2 (recommended):

[mcp_servers.rootly]

url = "https://mcp.rootly.com/mcp"

With API Token:

[mcp_servers.rootly]

url = "https://mcp.rootly.com/mcp" bearer_token_env_var = "ROOTLY_API_TOKEN"

Claude Desktop

With OAuth2 (recommended):

Add to claude_desktop_config.json:

{

"mcpServers": { "rootly": { "url": "https://mcp.rootly.com/mcp" } } }

Claude Desktop handles OAuth2 login automatically.

With API Token (via mcp-remote):

{

"mcpServers": { "rootly": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.rootly.com/mcp", "--transport", "http", "--header", "Authorization: Bearer " ] } } }

Databricks

Register the hosted server in Unity Gateway so Supervisor Agent, AI Playground, and other Databricks agents can use it:

1. In your workspace, open Unity Gateway > MCPs, click + MCP, and choose Connect an existing MCP server.
2. Pick a catalog and schema, name the MCP, and create a new connection with URL https://mcp.rootly.com/mcp.
3. Choose an authentication method:

• Dynamic Client Registration (recommended): each user signs in to Rootly with their own account.
• Bearer token: paste a Rootly API token.

1. Click Create & load tools, click Login if prompted, and select the tools to expose.

Or create the connection with the Databricks SDK:

from databricks.sdk import WorkspaceClient

from databricks.sdk.service import catalog as c

WorkspaceClient().connections.create( name="rootly_connection", parent="schemas/main.default", connection_type=c.ConnectionType.HTTP, options={ "host": "https://mcp.rootly.com", "port": "443", "base_path": "/mcp", "bearer_token": " ", }, )

The full profile exposes about 250 tools. Use Unity Gateway tool selection to expose only what your agents need. See docs/databricks-marketplace.md for the Marketplace listing details.

Rootly CLI

Standalone CLI for incidents, alerts, services, and on-call operations.

Install via Homebrew:

brew install rootlyhq/tap/rootly-cli

Or via Go:

go install github.com/rootlyhq/rootly-cli/cmd/rootly@latest

For more details, see the Rootly CLI repository.

Alternative Installation (Local)

Run the MCP server locally if you do not want to use the hosted service.

Prerequisites

• Python 3.12 or higher
• uv package manager

  curl -LsSf https://astral.sh/uv/install.sh | sh

• Rootly API token

API Token Types

Choose the token type based on the access you need:

• Global API Key: Full access across the Rootly instance. Best for organization-wide visibility.
• Team API Key: Access limited to entities owned by that team.
• Personal API Key: Access matches the user who created it.

A Global API Key is recommended for organization-wide queries and for actions that modify data, especially when workflows may span multiple teams, schedules, or incidents.

With uv

{

"mcpServers": { "rootly": { "command": "uv", "args": [ "tool", "run", "--from", "rootly-mcp-server", "rootly-mcp-server" ], "env": { "ROOTLY_API_TOKEN": " ", "ROOTLY_MCP_ENABLE_WRITE_TOOLS": "true" } } } }

Self-Hosted Transport Options

Choose one transport per server process:

• Streamable HTTP endpoint path: /mcp
• SSE (deprecated, removed after 2026-11-20) endpoint path: /sse. --transport sse logs a deprecation warning at startup; use --transport streamable-http instead.
• Code Mode (experimental) endpoint path: