Rootly MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Rootly MCP Server?

Rootly MCP Server is a server designed to integrate with the Rootly API, allowing users to resolve production incidents quickly within their favorite MCP-compatible editors like Cursor and Windsurf.

how to use Rootly MCP Server?

To use the Rootly MCP Server, install it via the PyPi package or clone the repository. Set it up in your MCP-compatible editor by configuring the server with your Rootly API token and desired settings.

key features of Rootly MCP Server?

  • Dynamically generates MCP resources based on Rootly's OpenAPI specification.
  • Default pagination for incident endpoints to manage context size.
  • Limits the number of API paths exposed for security and performance reasons.

use cases of Rootly MCP Server?

  1. Quickly resolving production incidents without leaving the IDE.
  2. Integrating incident management tools into development workflows.
  3. Customizing API access for enhanced security and performance.

FAQ from Rootly MCP Server?

  • Is Rootly MCP Server suitable for production use?

No, it is a prototype and not intended for production use.

  • How can I customize the API paths?

You can edit the allowed_paths variable in the server configuration file to expose more paths.

  • What are the prerequisites for using Rootly MCP Server?

You need Python 3.12 or higher and the uv package manager.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago