Productivity · Remote MCP server
Rootly
Incident management, on-call scheduling, and analysis powered by Rootly.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.rootly/mcp-server- Version
- 2.2.4
- Status
- Active
- Category
- productivity
- Transport
- SSE (HTTP + Server-Sent Events), stdio (local process)
- Package
- PyPI
- Published
- 2026-02-18
- Updated
- 2026-02-18
- Publisher
- com.rootly
- Namespace
- Namespace verified by the MCP Registry via the domain rootly.com · how
- Repository
- github.com/Rootly-AI-Labs/Rootly-MCP-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| SSE (HTTP + Server-Sent Events) | https://mcp.rootly.com/sse | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- SSE stream
- Not opened: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | rootly-mcp-server | 2.2.4 | stdio |
How to connect Rootly
Rootly is a remote MCP server reached over the older SSE transport, at https://mcp.rootly.com/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
It can also run locally from a Python package published to PyPI: rootly-mcp-server version 2.2.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx rootly-mcp-server. It reads the environment variable ROOTLY_API_TOKEN (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp-server": {
"command": "uvx",
"args": [
"rootly-mcp-server"
],
"env": {
"ROOTLY_API_TOKEN": "<secret>"
}
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| Roistat MCPMCP server for Roistat API - marketing analytics, visits tracking. API key auth. | Local · stdio |
| Roleset - job postings indexSearch 690k open jobs from official ATS feeds, and what changed since your last check. | Remote · HTTPLive check: ✓ handshake |
| rolnia.comProfile, CV, jobs, compensation & application-tracking tools for AI agents, by rolnia.com. | Local · stdio |
| RoomtoneAsk Claude about your meetings: summaries, action items and transcripts from Roomtone. | Remote · HTTPLive check: sign-in required |
| RootrConnect your team's living knowledge base - docs, data, issues, CRM - to Claude and ChatGPT. | Remote · HTTPLive check: sign-in required |
| RoryPlansAI work orchestration for plans, tasks, teams, and coding-agent dispatch. | Remote · HTTPLive check: sign-in required |
| Rosetta PDFParse, extract, split, and ask over digital PDFs (text layer, no OCR) from Cursor and Claude. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Router MCPRun the Intelliverse platform from any agent: apps, API keys, knowledge bases, email, media, chat. | Local · stdio |