Rootly
概览
作者提供的说明(英文原文)
Incident management, on-call scheduling, and intelligent analysis powered by Rootly.
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i1 项中通过 1 项依据公开信息检查;尚未扫描代码
- 使用情况i起步阶段↓ 1242/周 · ★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
安装
选择你使用的 AI 应用,然后复制设置。
安装之前
- 基础检查:1 项中通过 1 项
- 在作者的服务器上运行:你向它提出的内容会经过他们的服务器。
- 需要你自己填写:
ROOTLY_API_TOKEN,Authorization
标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
或者在你的电脑上运行
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"rootly": {
"command": "uvx",
"args": [
"rootly-mcp-server"
],
"env": {
"ROOTLY_API_TOKEN": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport sse rootly https://mcp.rootly.com/sse --header 'Authorization: your-value'或者在你的电脑上运行
claude mcp add rootly --env ROOTLY_API_TOKEN=your-value -- uvx rootly-mcp-server运行前请先填写空着的值。
或者自己复制设置
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"rootly": {
"url": "https://mcp.rootly.com/sse",
"headers": {
"Authorization": "your-value"
}
}
}
}或者在你的电脑上运行
或者自己复制设置
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"rootly": {
"command": "uvx",
"args": [
"rootly-mcp-server"
],
"env": {
"ROOTLY_API_TOKEN": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"rootly": {
"type": "sse",
"url": "https://mcp.rootly.com/sse",
"headers": {
"Authorization": "your-value"
}
}
}
}或者在你的电脑上运行
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"rootly": {
"type": "stdio",
"command": "uvx",
"args": [
"rootly-mcp-server"
],
"env": {
"ROOTLY_API_TOKEN": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
需要你填写的值
- Your Rootly API token
Authorization机密 必填 HTTP headerBearer token for Rootly API (format: Bearer )
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它能做什么
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
- ✓ 通过
作者与仓库一致
注册名称已通过域名 rootly.com 验证(注册中心会核实域名所有权)
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
端点有响应
尚未检查;我们会轮流检查各个端点
- … 尚未检查
使用 OAuth 登录
尚未检查;我们会轮流检查各个端点
- … 尚未检查
工具描述中没有隐藏指令
尚未检查;我们会在检查端点时读取工具列表
与“文档、表格与办公”中的其他服务器比较i
- 星标数多于此分类中其他 3572 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 3572 个服务器的 2% 更新
- 基础检查结果等于或优于此分类中其他 3572 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
Rootly 安全吗?
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
你需要填写:ROOTLY_API_TOKEN, Authorization
它在我的电脑上运行还是在云端?
两种方式都可以:安装在你的电脑上,或者连接云端版本。
它还在维护吗?
GitHub 仓库最后更新于–,最新版本(2.2.4)于9个月前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
有什么可以替代它?
同一分类中有:Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
替代选择
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Excel MCP Server
Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.
MCP Server for Excel
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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/sseendpoint and the self-hosted--transport sseoption 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 tohttp/streamable-http. SSE responses now carryDeprecation,SunsetandLink: 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.
| Toolset | What it covers |
|---|---|
core (recommended) | Everyday incident response: find and update incidents, alerts, who is on call (~29 tools) |
incidents | Action items, events, roles, retrospectives, form field selections, meeting recordings |
alerts | Alerts, alert sources, routes and routing rules, urgencies, heartbeats, live call routers |
oncall | Schedules, rotations, shifts, overrides, escalation policies and paths |
workflows | Workflows, workflow tasks and runs, playbooks |
catalog | Services, functionalities, teams, environments, catalogs |
status_pages | Status pages, templates, pulses |
config | Severities, causes, incident types, forms, retrospective processes, dashboards |
users | Users, notification rules, contact methods |
ai | AI SRE investigations, AI automations and skills |
observability | Rootly Observability logs and patterns |
audit | Audit log |
- Pick toolsets:
https://mcp.rootly.com/mcp?toolsets=core,workflows, or sendX-MCP-Toolsets: core,workflows - Everything:
?toolsets=all(about 280 tools) - Read-only: add
readonly=true(orX-MCP-Readonly: true), e.g.?toolsets=all&readonly=true. Any value other thanfalse/0/no/offturns 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/allmean?toolsets=all;slimkeeps 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,alertssets what a client gets with no selection (defaultall);ROOTLY_MCP_HOSTED_TOOL_PROFILE=slimmakes 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:
- In your workspace, open Unity Gateway > MCPs, click + MCP, and choose Connect an existing MCP server.
- Pick a catalog and schema, name the MCP, and create a new connection with URL
https://mcp.rootly.com/mcp. - 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.
- 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
uvpackage manager
curl -LsSf https://astral.sh/uv/install.sh | sh
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 sselogs a deprecation warning at startup; use--transport streamable-httpinstead. - Code Mode (experimental) endpoint path:
/mcp-codemodein hosted dual-transport mode. Oneexecutecall may make at most 50 tool calls; setROOTLY_CODE_MODE_MAX_TOOL_CALLSto a positive integer to change that.
- Hosted default: full surface;
?toolsets=corefor the recommended small one (see Toolsets) - Hosted slim profile (deprecated): about 85 high-usage tools via
?tool_profile=slim - Self-hosted default: full surface (
ROOTLY_MCP_TOOLSETSnarrows it)
To restrict either deployment to read-only tools, st
只显示了开头部分;其余内容请在仓库中阅读