red for Claude Desktop. If you installed manually, add the following to your `claude_desktop_config.json`: ```json { "mcpServers": { "uptime-agent": { "command": "npx", "args": [ "-y", "uptime-agent-mcp" ], "env": { "UPTIME_API_KEY": "" } } } } ``` Alternatively, you can use Docker: ```json { "mcpServers": { "uptime-agent": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "UPTIME_API_KEY", "uptime-agent-mcp" ], "env": { "UPTIME_API_KEY": "" } } } } ``` ### Example Conversations **Checking Monitors:** > "Claude, show me all my active uptime monitors." **Creating a New Monitor:** > "Please create a new monitor for our API endpoint at https://api.mycompany.com/v2/health" **Analyzing Incidents:** > "What incidents happened on our production servers last week, and what was the average downtime?" ## 📊 Available Functions ### Monitor Operations | Function | Description | Parameters | |----------|-------------|------------| | `listMonitors` | Get a complete list of all monitoring endpoints | None required | | `getMonitor` | Retrieve detailed information about a specific monitor | `id`: Monitor identifier | | `createMonitor` | Set up a new endpoint to monitor | `name`: Monitor name
`url`: URL to monitor
`tracking_type`: Type of monitoring (http, ping, etc.)
`check_frequency`: Check interval in seconds | ### Incident Management | Function | Description | Parameters | |----------|-------------|------------| | `listIncidents` | View all detected downtime incidents | None required | | `getIncident` | Get detailed information about a specific incident | `id`: Incident identifier | | `listIncidentsByMonitor` | See all incidents for a particular endpoint | `monitor_id`: Monitor identifier | ### Public Tracking | Function | Description | Parameters | |----------|-------------|------------| | `createAnonymousTracking` | Create public tracking without authentication | `url`: URL to monitor
`name`: (Optional) Name for the tracking | ### Integration with Slack (Coming Soon) | Function | Description | Parameters | |----------|-------------|------------| | `slack_get_users` | List all users in connected Slack workspace | `limit`: Max number of users
`cursor`: Pagination cursor | | `slack_post_message` | Post notifications to Slack | `channel_id`: Channel to post to
`text`: Message content | ## 🐳 Docker Deployment We provide Docker support for easy deployment: ```bash # Build the Docker image docker build -t uptime-agent-mcp . # Run the container docker run -p 3000:3000 -e UPTIME_API_KEY=your-api-key uptime-agent-mcp ``` ## 📬 Support If you have questions or need assistance: - [Open an issue](https://github.com/AVIMBU/uptime_agent_mcp/issues) on GitHub - Contact us through our website: [AVIMBU](https://avimbu.com) ## 📜 License This project is licensed under the MIT License - see the LICENSE file for details. ---

Developed with ❤️ by AVIMBU

25:T5ae,## 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 up

#uptime-monitor

🚀 Uptime Agent MCP Server