🚀 Uptime Agent MCP Server

Created By
AVIMBUa year ago
Connect your Uptime Agent monitoring system directly to AI assistants like Claude through the Model Context Protocol (MCP).
Overview

What is Uptime Agent MCP?

Uptime Agent MCP is a server that connects your Uptime Agent monitoring system directly to AI assistants like Claude through the Model Context Protocol (MCP). It enhances the monitoring experience by allowing users to interact with their monitoring systems using natural language.

How to use Uptime Agent MCP?

To use Uptime Agent MCP, you need to install it on your server, set up your Uptime Agent API key, and configure it to connect with AI assistants. You can interact with the system through voice or text commands to manage your monitoring endpoints.

Key features of Uptime Agent MCP?

  • Real-time monitoring access for uptime status checks
  • Incident management through natural conversation
  • Easy setup of new monitoring endpoints
  • Secure integration with enterprise-grade security

Use cases of Uptime Agent MCP?

  1. Checking the status of active uptime monitors.
  2. Creating new monitors for API endpoints.
  3. Analyzing downtime incidents through conversational queries.

FAQ from Uptime Agent MCP?

  • Can I use Uptime Agent MCP without an Uptime Agent account?

No, you need an active Uptime Agent account to use this service.

  • Is there a cost associated with using Uptime Agent MCP?

The Uptime Agent service may have associated costs depending on your usage and plan.

  • What programming language is Uptime Agent MCP built with?

Uptime Agent MCP is built with TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
AVIMBU
Star
0
Language
JavaScript
License
-
Category
monitoring

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