How to connect the Rootly MCP server
To connect the official Rootly MCP server, follow Rootly's setup instructions, then sign in with OAuth when your client prompts you. Add https://mcp.rootly.com/mcp as a remote MCP server that uses the Streamable HTTP transport (often labelled "http"). Rootly also documents a Code Mode endpoint, https://mcp.rootly.com/mcp-codemode, which it recommends, and a toolsets query parameter on the /mcp endpoint (core or all) to choose how many tools are exposed. The Registry entry still lists the deprecated SSE endpoint, https://mcp.rootly.com/sse, which Rootly says it will remove after November 20, 2026. If your client can't use OAuth, use a Rootly API token. Rootly documents setup for Claude Code, Cursor, Windsurf, Codex and Claude.
Docs reviewed 5 Nov 2026Not a tested connection.
Registry endpoint https://mcp.rootly.com/sse · Registry com.rootly/mcp-server 2.2.4
Add Rootly MCP to your client
The Registry endpoint (https://mcp.rootly.com/sse, sse) isn't ready to paste into a client. Follow the steps and Rootly's own instructions for the address to use.
Connect Rootly MCP step by step
Before you start
- A Rootly login that can grant consent in the OAuth window, or an active Rootly API key if you use a token instead. docs.rootly.com/integrations
- If you use an API token, Rootly recommends a Global API Key. A Team API Key is scoped to one team and can return incomplete data from on-call tools that need organization-wide visibility. A Personal API Key inherits the creating user's permissions. docs.rootly.com/integrations
- The SSE endpoint is deprecated and Rootly says it will be removed after November 20, 2026. Use the Streamable HTTP endpoint. docs.rootly.com/integrations
Authentication
- Your client → Rootly MCP
- OAuth sign-in, handled by your MCP client. docs.rootly.com/integrationsmodelcontextprotocol.io/specification
- Rootly MCP → Rootly API
- The server acts on your account with the access you approve. docs.rootly.com/integrations
Steps
- Open Rootly's MCP server setup instructions
- Add the Rootly MCP server to your client
Add https://mcp.rootly.com/mcp as a remote MCP server that uses the Streamable HTTP transport (often labelled "http"). Rootly also documents a Code Mode endpoint, https://mcp.rootly.com/mcp-codemode, which it recommends, and a toolsets query parameter on the /mcp endpoint (core or all) to choose how many tools are exposed. The Registry entry still lists the deprecated SSE endpoint, https://mcp.rootly.com/sse, which Rootly says it will remove after November 20, 2026.
- Sign in to Rootly and grant access in the OAuth window
- If your client can't use OAuth, use a Rootly API token
Generate an API key in Rootly under Account, Manage API keys, Generate New API Key. Send it in the Authorization header as a bearer token. Keep the key in an environment variable or secret store, not in shared configuration. Rootly recommends a Global API Key for organization-wide tools.
- Only with an API token: Authorization header
- List the server's tools
Your client should list the server's tools. That confirms the connection, not every API permission.
What we observed
- 5 Nov 2026: HTTP 401 on https://mcp.rootly.com/sse with WWW-Authenticate resource_metadata https://mcp.rootly.com/.well-known/oauth-protected-resource, plus Deprecation and Sunset (Fri, 20 Nov 2026) headers and a successor-version link to https://mcp.rootly.com/mcp. The /mcp endpoint returns the same 401 and resource_metadata. The metadata names the authorization server https://rootly.com and scopes openid, profile, email and all.
Rootly MCP questions
What is the Rootly MCP server URL?
Rootly's MCP Registry record lists https://mcp.rootly.com/sse (SSE), but that address isn't ready to use as-is. Add https://mcp.rootly.com/mcp as a remote MCP server that uses the Streamable HTTP transport (often labelled "http"). Rootly also documents a Code Mode endpoint, https://mcp.rootly.com/mcp-codemode, which it recommends, and a toolsets query parameter on the /mcp endpoint (core or all) to choose how many tools are exposed. The Registry entry still lists the deprecated SSE endpoint, https://mcp.rootly.com/sse, which Rootly says it will remove after November 20, 2026.
How do I authenticate with the Rootly MCP server?
Sign in with OAuth when your client prompts you. If your client can't use OAuth, use a Rootly API token: Generate an API key in Rootly under Account, Manage API keys, Generate New API Key. Send it in the Authorization header as a bearer token. Keep the key in an environment variable or secret store, not in shared configuration. Rootly recommends a Global API Key for organization-wide tools.
Which AI clients can use the Rootly MCP server?
Rootly's documentation covers Claude Code, Cursor, Windsurf, Codex and Claude. Other clients that support remote SSE MCP servers may also work.
What do I need before connecting Rootly MCP?
A Rootly login that can grant consent in the OAuth window, or an active Rootly API key if you use a token instead. If you use an API token, Rootly recommends a Global API Key. A Team API Key is scoped to one team and can return incomplete data from on-call tools that need organization-wide visibility. A Personal API Key inherits the creating user's permissions. The SSE endpoint is deprecated and Rootly says it will be removed after November 20, 2026. Use the Streamable HTTP endpoint.
Has this Rootly MCP guide been tested?
Rootly's documentation was reviewed on 2026-11-05. It is not a tested connection; your account and permissions decide which tools work.
Sources and review
Rootly's documentation was checked on the dates shown. This guide follows the MCP Connect connection-guide draft, bound to the exact Registry record it describes. It is not a tested connection: your account and permissions decide which tools work.
Guide source and binding
MCP connection guide (draft 0.1) for com.rootly/mcp-server 2.2.4, bound to /remotes/0 of the Registry record by SHA-256 427029100549….
- docs.rootly.com/integrations/mcp-server · checked 5 Nov 2026
- registry.modelcontextprotocol.io/v0.1/servers/com.rootly%2Fmcp-server/versions/2.2.4 · checked 5 Nov 2026
- modelcontextprotocol.io/specification/2026-07-28/basic/authorization · checked 5 Nov 2026