{
  "markdown": "# UptyBots MCP Server\n\nConnect AI assistants like **Claude**, **Cursor**, and other MCP-compatible tools to your [UptyBots](https://uptybots.com) uptime monitors.\n\n## What is this?\n\nAn [MCP (Model Context Protocol)](https://modelcontextprotocol.io) server that gives AI assistants access to your UptyBots monitoring data. Ask your AI to check monitor status, review incidents, create new monitors, and more - through natural conversation.\n\n## You probably want the hosted server instead\n\nThere is now a remote server that needs no install and no API key:\n\n```\nhttps://mcp.uptybots.com/mcp\n```\n\nAdd that URL to your client and it opens a browser for you to sign in and approve\naccess. If you do not have an UptyBots account yet, you can create one at that step.\n\nWith Claude Code:\n\n```bash\nclaude mcp add --transport http uptybots https://mcp.uptybots.com/mcp\n```\n\nthen run `/mcp`, pick **uptybots** and authenticate.\n\n**This package is the local alternative.** It runs on your own machine and\nauthenticates with an API key instead of a browser sign-in - the right choice for\nMCP clients that cannot talk to remote servers, and for offline or self-contained\nsetups. It exposes the same 15 tools and is not going away.\n\n## Prerequisites\n\n- [Node.js](https://nodejs.org/) 18 or later\n- A [UptyBots](https://uptybots.com) account\n- An API key from [Account → API Keys](https://uptybots.com/account/api-keys)\n\n## Setup\n\n### 1. Configure your AI client\n\nNo install step needed: `npx` fetches the published package on first run.\n\nAdd to your MCP client configuration:\n\n**Claude Desktop** (`claude_desktop_config.json`):\n\n```json\n{\n  \"mcpServers\": {\n    \"uptybots\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"uptybots-mcp-server\"],\n      \"env\": {\n        \"UPTYBOTS_API_URL\": \"https://uptybots.com\",\n        \"UPTYBOTS_API_KEY\": \"upty_your_api_key_here\"\n      }\n    }\n  }\n}\n```\n\n**Claude Code** (`~/.claude/settings.json`) and **Cursor** (`.cursor/mcp.json`) use the same format.\n\n### 2. Restart your AI client\n\nThe MCP tools will be available immediately.\n\n### Running from source (optional)\n\nTo run a local checkout instead of the npm package:\n\n```bash\ngit clone https://github.com/uptybots/mcp-server.git\ncd mcp-server\nnpm install\n```\n\nThen point the client at the checkout:\n\n```json\n{\n  \"mcpServers\": {\n    \"uptybots\": {\n      \"command\": \"node\",\n      \"args\": [\"/path/to/mcp-server/index.js\"],\n      \"env\": {\n        \"UPTYBOTS_API_URL\": \"https://uptybots.com\",\n        \"UPTYBOTS_API_KEY\": \"upty_your_api_key_here\"\n      }\n    }\n  }\n}\n```\n\n## Available Tools (15)\n\n### Read\n| Tool | Description |\n|------|-------------|\n| `list_monitors` | List all monitors with filters (type, status) |\n| `get_monitor` | Get monitor details by ID |\n| `get_incidents` | Get downtime incidents for a monitor |\n| `get_stats_hourly` | Hourly performance stats |\n| `get_stats_daily` | Daily performance stats |\n| `get_notifications` | Notification history |\n\n### Create\n| Tool | Description |\n|------|-------------|\n| `create_http_monitor` | Create HTTP/HTTPS monitor |\n| `create_api_monitor` | Create API endpoint monitor |\n| `create_ping_monitor` | Create ICMP ping monitor |\n| `create_port_monitor` | Create TCP port monitor |\n| `create_ssl_monitor` | Create SSL certificate monitor |\n| `create_domain_monitor` | Create domain expiration monitor |\n\n### Manage\n| Tool | Description |\n|------|-------------|\n| `pause_monitor` | Pause a monitor |\n| `resume_monitor` | Resume a paused monitor |\n| `delete_monitor` | Delete a monitor |\n\n## Prompts (5)\n\nStarting sentences an assistant can offer instead of asking you to phrase the request\nyourself. Each one is a wording of something the tools above already do; none adds\ncapability. The hosted server offers exactly the same five.\n\n| Prompt | Argument | What it asks for |\n|--------|----------|------------------|\n| `status_check` | none | What is failing right now, and since when |\n| `uptime_report` | `days` (optional, default 7) | Uptime and response times over a period, worst first |\n| `incident_review` | `monitor` | The failure pattern of one monitor: outage, flapping, or degradation |\n| `expiry_audit` | none | SSL certificates and domains by how soon they expire |\n| `setup_monitor` | `target` | The right monitor type for a target, then create it |\n\n## Environment Variables\n\n| Variable | Required | Description |\n|----------|----------|-------------|\n| `UPTYBOTS_API_URL` | No | API base URL (default: `https://uptybots.com`) |\n| `UPTYBOTS_API_KEY` | Yes | Your API key (starts with `upty_`) |\n\n## Documentation\n\n- [MCP Server Docs](https://uptybots.com/docs/mcp) - full setup guide and tool reference, covering both the hosted server and this one\n- [REST API Reference](https://uptybots.com/docs/api) - the API that powers the MCP server\n- [Account → Connected Applications](https://uptybots.com/account/connected-apps) - review and revoke access granted through the hosted server\n\n## License\n\nMIT",
  "bytes": 4938,
  "sha": "925989ed65aed5b8414890ab153833ac5e08d32a215d0836c7a0c21e83376227",
  "repo_slug": "uptybots/mcp-server",
  "fonte": "npm",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_com_uptybots_monitoring_01ddca91/readme"
}