Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Monitor websites, APIs, and servers: create monitors, triage incidents, and query uptime stats.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:
https://mcp.uptimerobot.com/mcp터미널에서 이 명령어를 실행하세요
claude mcp add --transport http uptimerobot https://mcp.uptimerobot.com/mcp프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"uptimerobot": {
"url": "https://mcp.uptimerobot.com/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"uptimerobot": {
"type": "http",
"url": "https://mcp.uptimerobot.com/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:
https://mcp.uptimerobot.com/mcp메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
레지스트리 이름이 도메인 uptimerobot.com 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.1.0)은 3개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, LickityClick
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Create, edit and track LickityClick short links, campaigns and click stats from your AI assistant.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
This repo is UptimeRobot's single source of truth for AI agent integrations. It publishes:
.mdc). Claude Code gets the same rules from the conventions skill.The mcp.json and .mcp.json files both connect directly to the hosted server at https://mcp.uptimerobot.com/mcp over streamable HTTP. Nothing runs locally: the client discovers the server's OAuth endpoints and runs the browser login itself. Two filenames exist only because Cursor expects the dot-less name and Claude Code and Codex the dot-prefixed one.
The same content is mirrored under uptimerobot.com/ for crawler discovery (uptimerobot.com/llms.txt, uptimerobot.com/AGENTS.md, etc.).
UptimeRobot is being submitted to Anthropic's community plugin marketplace. Once accepted, add that marketplace once and install:
/plugin marketplace add anthropics/claude-plugins-community
/plugin install uptimerobot@claude-community
Or run /plugin, open the Discover tab, find UptimeRobot, and install it. (The community marketplace must be added first — it isn't built in. Only Anthropic's curated official marketplace shows up in /plugin with no setup.)
The MCP server auto-registers via .mcp.json as soon as the plugin loads. The first time it connects, a browser opens for you to log into UptimeRobot and authorize access (OAuth) — there's no API key to paste. Tokens are cached locally, so you only do this once.
To run the full plugin (skills and the auto-registered MCP server) straight from a local checkout — no marketplace required — clone the repo and load it with the --plugin-dir flag:
git clone https://github.com/uptimerobot/ai.git
claude --plugin-dir ./ai
--plugin-dir loads the plugin from a directory (the one containing .claude-plugin/plugin.json) for that session only. The flag is repeatable and also accepts a .zip. Use an absolute path if you launch Claude Code from elsewhere:
claude --plugin-dir /absolute/path/to/ai
On first connection a browser opens for the OAuth flow. Run /plugin to confirm the plugin is loaded and uptimerobot MCP Server shows ✓ connected.
If you just want the MCP tools without the rest of the plugin (dotfiles, CI bootstrap), register the server yourself:
claude mcp add --transport http uptimerobot https://mcp.uptimerobot.com/mcp
Then run /mcp, select uptimerobot, and choose Authenticate to complete the OAuth browser flow. Run /mcp (or claude mcp list in a terminal) to confirm uptimerobot shows ✓ connected.
Browse the Cursor Marketplace, find UptimeRobot, and click Add to Cursor. Authorize through the OAuth browser flow when the MCP server first connects — no API key needed.
Follow Cursor's plugin docs:
# Clone or symlink this repo into Cursor's local plugin folder
git clone https://github.com/uptimerobot/ai.git ~/.cursor/plugins/local/uptimerobot-ai
Launch Cursor and run Developer: Reload Window from the command palette.
Verify the plugin is discovered:
uptimerobot.mdc rule and every skills/*/SKILL.md entry should be listed.uptimerobot should appear with up to 60 tools (fewer for read-only or team sessions) once the MCP server connects. Complete the OAuth browser flow on first connection.Clone the repo and open it in Codex. The repo-scoped marketplace at .agents/plugins/marketplace.json is auto-discovered, so UptimeRobot (local) will appear in the Codex plugin directory without any extra setup. Install the plugin, then complete the OAuth browser flow on first MCP connection.
If you want Codex to track the source explicitly:
codex plugin marketplace add ./
Verify the plugin is loaded: the UptimeRobot skills should be available and the uptimerobot MCP server should appear with up to 60 tools (fewer for read-only or team sessions) once connected.
The server is listed in the official MCP Registry as com.uptimerobot/uptimerobot, so any registry-aware client can discover and install it without a per-client plugin submission. Metadata lives in server.json:
curl -s "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.uptimerobot/uptimerobot"
Clients without registry support can connect to the same URL directly (OAuth on first use):
{
"mcpServers": { "uptimerobot": { "type": "http", "url": "https://mcp.uptimerobot.com/mcp" } } }
Where the OAuth browser flow can't run, add the server to your own client config with an API key from the dashboard (Integrations & API) instead — a Read-only key unless the job needs to write. Keep the key in an environment variable, not in the file, and never commit it. This is a manual setup — the plugin itself never reads or sends an API key:
{
"mcpServers": { "uptimerobot": { "type": "http", "url": "https://mcp.uptimerobot.com/mcp", "headers": { "Authorization": "Bearer ${UPTIMEROBOT_API_KEY}" } } } }
Claude Code expands ${UPTIMEROBOT_API_KEY} from the environment; other clients have their own syntax (Cursor: ${env:UPTIMEROBOT_API_KEY}).
60 tools via MCP, grouped by resource — full list in AGENTS.md; each tool's own schema and description are the reference for its parameters:
| Tool | Purpose |
|---|---|
create-monitor | Create HTTP, KEYWORD, PING, PORT, HEARTBEAT, DNS, API, or UDP monitors |
update-monitor | Change name, URL, interval, alert contacts, tags, HTTP settings (list and map fields replace the whole value — see AGENTS.md) |
update-monitor-status | Pause or resume a monitor |
list-monitors | Paginated list filtered by name, URL, tags, group, custom field, or state |
get-monitor-details | Full config + current state for one monitor |
get-monitor-stats | Aggregated up/down/paused counts + uptime (a 0–1 fraction) |
get-response-times | Time-series response-time data with buckets |
delete-monitor | Permanently delete a monitor and its history |
monitor-groups)| Tool | Purpose |
|---|---|
create-monitor-group | Create a group and assign monitors to it |
update-monitor-group | Rename an existing group |
delete-monitor-group | Delete a group; its monitors move to another group or none |
get-monitor-group | Fetch a single group by ID |
list-monitor-groups | Paginated list of groups |
| Tool | Purpose |
|---|---|
create-psp | Create a status page from monitors, groups, or tags (always created public; pause with update-psp) |
update-psp | Change name, domain, sort order, visibility, publish status, or monitors (monitor lists replace the whole list) |
get-psp | Fetch a single status page by ID |
list-psps | Paginated list of status pages |
delete-psp | Permanently delete a status page |
psp-subscribers)| Tool | Purpose |
|---|---|
create-psp-announcement | Post an announcement (info/maintenance/issue) to a status page |
update-psp-announcement | Edit title, content, dates, type, or publish status |
pin-psp-announcement | Pin an announcement to the top of the page |
unpin-psp-announcement | Unpin an announcement |
get-psp-announcement | Fetch a single announcement by ID |
list-psp-announcements | Paginated list of announcements for a status page |
delete-psp-announcement | Permanently delete an announcement |
maintenance-window)| Tool | Purpose |
|---|---|
create-maintenance-window | Schedule a one-off or recurring window that suppresses alerts |
update-maintenance-window | Change schedule, duration, monitors, or pause/resume the window |
get-maintenance-window | Fetch a single window by ID |
list-maintenance-windows | Paginated list of windows |
delete-maintenance-window | Permanently delete a window |
| Tool | Purpose |
|---|---|
list-incidents | Incidents across monitors, with time range, monitor, or open-only filter |
get-incident-details | Per-incident request logs and cause |
get-incident-activity-log | Incident timeline summary plus paginated entries |
get-incident-alerts | Alerts sent during an incident, with delivery summary |
incident-comments)| Tool | Purpose
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요