Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 4
- 4 1
- 3 1
- 2 0
- 1 0
Trust in production
- Trust it - 83%
- With caveats - 17%
- Wouldn't - 0%
83% would recommend this server
How reviewers scored it
- Setup & docs 4.2
- Auth experience 4.7
- Reliability 4.7
- Maintainer responsiveness 4.5
Why it got an A
Rootly's own server, open source (Apache-2.0) in rootlyhq/rootly-mcp-server and on PyPI as rootly-mcp-server. This grade describes that code. The README presents the hosted endpoint at https://mcp.rootly.com/mcp as the same package run as a service, but we can't see the build Rootly actually deploys, so the hosted service is scored from the repo and its docs. Hosted sign-in uses OAuth2 (recommended); the alternative is a Rootly API key (global, team or personal) as a Bearer token, so keep to a team or personal key rather than a global one. Biggest caution: with no toolset chosen you get every tool, about 280, including ones that create and update incidents, change on-call schedules and set up workflow steps that can page people, and the docs don't say whether the server asks before a write. Add ?toolsets=core (about 29 tools) and readonly=true to the URL, which hides write tools and refuses non-GET calls on that connection, and keep tool approval on in your client. The self-hosted server also has write tools switchable with ROOTLY_MCP_ENABLE_WRITE_TOOLS. Hosted SSE is deprecated and removed after 2026-11-20; use the HTTP URL.
How to connect
Hosted: claude mcp add --transport http rootly https://mcp.rootly.com/mcp (OAuth2 sign-in); or self-hosted: uv tool run --from rootly-mcp-server rootly-mcp-server with ROOTLY_API_TOKEN setIs Rootly MCP Server safe?
Is Rootly MCP Server safe to use?
Rootly MCP Server grades A: all four checks are at full marks. Strong public trust signals. It is still not a full audit, so give it the narrowest access that works.
Does Rootly MCP Server have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does Rootly MCP Server support authentication?
Yes. It requires a login, so access can be tied to a person or a scoped key.
Alternatives in Developer Tools
- A Amplitude MCP ServerAmplitude's hosted MCP server for product analytics - search and query events, charts, dashboards, experiments, feature flags, cohorts and session replay, with OAuth sign-in and a separate EU endpoint.
- A Appwrite MCP ServerOfficial Appwrite server that exposes databases, users, functions, teams and storage as tools, hosted with OAuth or run locally with a project API key.
- A Atlassian Rovo MCP ServerOfficial hosted Atlassian server for Jira, Confluence, Jira Service Management, Compass, Bitbucket, Loom, Goals, Projects, and Teams, with OAuth 2.1 sign-in.
- A Better Stack MCP ServerOfficial hosted Better Stack server to read and manage incidents, monitors, status pages and on-call, and run SQL over your logs, spans and metrics, with OAuth or an API token.
- A Buildkite MCP ServerOfficial Buildkite server for pipelines, builds, jobs, logs, annotations, and Test Engine data, hosted or local.
Embed this badge
[](https://trustedmcp.io/servers/rootly-mcp)<a href="https://trustedmcp.io/servers/rootly-mcp"><img src="https://trustedmcp.io/badge/rootly-mcp.svg" alt="TrustedMCP grade A" height="80"></a>Community reviews
Trustworthy enough for real work
Installed it on a Friday, it was part of my workflow by Monday. I like that access goes through a proper sign-in instead of a long-lived secret on disk. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Good choice if you need Rootly in your agent.
Used for Code review summaries for pull requests
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 5/5
- Maintainer responsiveness 3/5
Set it up once, forgot about it
Hooked Rootly MCP Server into Claude Code and it worked on the first try. Auth is handled properly, and revoking access later was one click. Filed an issue and got a reply within two days. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent.
Used for Onboarding new devs with an agent that answers repo questions
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Surprisingly polished
Tried it on a side project first, then rolled it out at work. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Self-hosting it was straightforward and I like keeping the data on our side. Easy recommendation.
Used for CI failure investigation
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Good, but read the permissions first
Took longer to configure than I expected. Releases come often and the changelog is clear. Sign-in flow was painless and I never had to paste a key into a config file.
Used for Keeping project tickets in sync with code changes
- Setup & docs 3/5
- Auth experience 5/5
- Reliability 3/5
- Maintainer responsiveness 5/5
Solid and well behaved
Our agents call this dozens of times a day. I like that access goes through a proper sign-in instead of a long-lived secret on disk. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. You can tell it is actively maintained, the rough edges keep getting fixed. It is in our production agent and I sleep fine.
Used for Looking up Rootly data without leaving the editor
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 4/5
No complaints after a month
Clear tool names, sensible outputs, very few surprises. Auth is handled properly, and revoking access later was one click. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. The API key sits in the config file, so I made a dedicated key with minimal permissions. Happy to run it in production.
Used for Pairing with Claude Code on a monorepo
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.