Supabase
by supabase
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
Computer or cloud★ 2,993Apache-2.0Updated yesterday
Install
Rootly MCP
Overview
Description from the maker (original English)
Every Rootly incident, alert, and on-call object as a typed command - plus a local SQLite mirror
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Databases & datasets
- You need to fill in: ROOTLY_API_KEY, ROOTLY_API_TOKEN
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
ROOTLY_API_KEY,ROOTLY_API_TOKEN,ROOTLY_BASE_URL
Values marked secret are keys to your account. Never share them or paste them into a chat.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Fill in the empty values before running it.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
- Set the ROOTLY_API_KEY credential for the Rootly MCP server.
- Set the ROOTLY_API_TOKEN credential for the Rootly MCP server.
ROOTLY_BASE_URLenvBase URL for the Rootly API. Leave the prefilled default unless your account uses a different regional or self-hosted host.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account servosity, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Databases & datasetsi
- More stars than 0% of the other 953 servers in this category
- Published to the registry more recently than 77% of the other 953 servers in this category
- Basic checks equal to or better than 100% of the other 953 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Rootly MCP safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: ROOTLY_API_KEY, ROOTLY_API_TOKEN
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.7) reached the registry 14 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
What can I use instead?
In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MongoDB MCP Server
by mongodb-js
MongoDB Model Context Protocol Server
Runs on your computer★ 1,157Apache-2.0Updated 2 days ago
Install
Elasticsearch MCP Server
by cr7258
MCP server for interacting with Elasticsearch
Runs on your computer★ 315Apache-2.0Updated 14 months ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Rootly + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP
Unofficial. Community-built Claude Code Skill and MCP server for the Rootly
API. Not affiliated with, endorsed by, or sponsored by Rootly, Inc..
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Every Rootly incident, alert, and on-call object as a typed command - plus a local SQLite mirror that answers related-incident, MTTR, coverage-gap, and on-call questions offline and instantly. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.
Works with your agent
Security note (until this connector is reprinted). Do not run HTTP mode
(
--transport http), not even on localhost. This build has no password,
listens on every network interface, and predates the browser-rebinding guard,
so a web page you open can reach it. The MCP tools can also make changes with
your credentials. Use the default stdio transport. If you set up a tunnel for
a remote agent, shut it down. A fix is on the way.
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the Rootly skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register rootly-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add rootly-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet. |
| Codex CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste the install prompt below. |
| GitHub Copilot (VS Code) | Run installer, add rootly-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs rootly-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server, and this connector's HTTP mode is paused until it is reprinted (see the security note in mcp-install.md), so msp-skills does not support it yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.
Also for the Microsoft and Google stacks
Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list. |
| Google Gemini | Gemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills yet. |
Skill-native agents (also covered): Hermes and OpenClaw read this skill's
SKILL.mddirectly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).
Run more than one agent? Install across all 51+ supported agents in one command:
npx skills add Servosity/msp-skills@latest(requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.
Install in 60 seconds
Fastest for Claude Desktop - one-click .mcpb
Claude Desktop bundle: the
.mcpblaunches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companionrootly-cli. Releases cut from 2026-09-18 on ship that CLI inside the bundle; older bundles contain only the MCP server, so if yours lacks the companion, run the Path A or Path B installer below first (or setROOTLY_CLI_PATHto an existing binary). Details: #331.
Download Rootly MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Rootly release on the releases page.)
Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:
/plugin marketplace add Servosity/msp-skills/plugin install rootly@msp-skills
Path A - paste one prompt into your AI agent (recommended)
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Rootly Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/rootly/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/rootly/install.ps1 | iex. Then authenticate per the README and runrootly-cli --helpto explore.
The same prompt works in any agent that can run shell.
Path B - run the installer yourself
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/rootly/install.ps1 | iexmacOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/rootly/install.sh)The installer drops both rootly-cli (the CLI) and rootly-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
rootly-cli --versionUpgrade to the latest version
The installer always fetches the current release - re-run it to upgrade:
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/rootly/install.sh)Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/rootly/install.ps1 | iexClaude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update rootly@msp-skills.
Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, or another MCP client
After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.
Install for Hermes
From the Hermes CLI:
hermes skills install servosity/msp-skills/skills/rootly --forceInside a Hermes chat session:
/skills install servosity/msp-skills/skills/rootly --forceHermes speaks MCP natively, so it can also use the rootly-mcp server directly - same install path, same env vars.
Install for OpenClaw
Tell your OpenClaw agent (copy this):
Install the rootly skill from https://github.com/servosity/msp-skills/tree/main/skills/rootly. The skill defines how its required CLI (
rootly-cli) can be installed via theopenclaw:frontmatter block.
OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.
Authenticate
Set the credentials the CLI needs (from your Rootly portal):
ROOTLY_API_KEY=<value> ROOTLY_API_TOKEN=<value> rootly-cli doctordoctor confirms the credentials work before you run anything that touches data. It exits 0 even when the credential is rejected, so scripts should add --fail-on error.
What this skill does
| Question your MSP keeps asking | Command |
|---|---|
| Who's on call right now across every service and schedule? | rootly-cli oncall-now |
| What past incidents are most similar to this one? | rootly-cli related |
| What actually fixed this service the last time it broke? | rootly-cli fixed-last-time |
| What's our MTTA and MTTR by service this quarter? | rootly-cli mttr --by service --since 90d |
| Where does an on-call schedule have an unstaffed gap? | rootly-cli coverage-gaps --days 14 |
| Is it safe to deploy this service right now? | rootly-cli deploy-guard |
| Which incidents are breaching or about to breach SLA? | rootly-cli sla-breach --within 2h |
| Which open action items are overdue, grouped by owner? | rootly-cli action-items-overdue --group-by owner |
| Draft a paste-ready post-mortem skeleton for this incident. | rootly-cli postmortem-skeleton |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
What makes this different
Most Rootly integrations and MCP servers proxy each question into a live API call. That's fine for one record. It dies at scale, when you're asking "what's our MTTR by service across the quarter?" or "which past incidents are most similar to this one?" - questions that otherwise mean a call per object or Rootly's own analytics surface.
This skill syncs Rootly into a local SQLite mirror with full-text search. Aggregate questions become one local SQL join: instant, offline, and the AI sees the answer, not the raw data. Compound commands like related, mttr, and coverage-gaps join across incidents, services, schedules, and on-call shifts - work a stateless API wrapper can't do.
The pain this closes
On-call is where good teams quietly bleed out. Recurring on-call burnout and alert-fatigue threads on r/sysadmin and r/sre - and the industry's annual Catchpoint SRE Report - tell the same story: responders field a flood of pages, only a handful matter, and the real incident hides in the noise. Then at the reliability review, the numbers leadership wants - MTTA, MTTR, who's carrying the on-call load - get hand-stitched from exports. And nobody notices the gap in next week's schedule until an incident finds it first.
For an MSP running incident response across many client services, that's three open loops at once: too much noise to triage, no cheap way to report on it, and no early warning when coverage lapses. This skill closes them from the terminal:
- `rootly-cli oncall-now` - who's on call right now across every schedule and service, escalation tier included.
- `rootly-cli mttr --by service --since 90d` - MTTA and MTTR per service, computed offline from synced incidents. Review numbers without the portal expedition.
- `rootly-cli coverage-gaps --days 14` - future wind
Only the beginning is shown; read the rest in the repo