What are the requirements for IonHour?

IonHour requires the following environment variables: IONHOUR_API_KEY (required). You'll also need a compatible MCP client like Claude Desktop or Claude Code.

Is IonHour free to use?

Yes, IonHour is open source and free to use. You can find the source code on GitHub.

What MCP clients support IonHour?

IonHour works with any MCP-compatible client including Claude Desktop (Anthropic's official desktop app), Claude Code (CLI tool), Cursor, and other editors with MCP support.

How do I configure IonHour?

Configure IonHour by adding it to your MCP client's config file. For Claude Desktop, edit claude_desktop_config.json and add the server configuration. See the Configuration section above for a ready-to-use example.

IonHour MCP Server

Q: What tools does IonHour provide?

get_workspace: Get workspace details. get_workspace_summary: Overview of projects, checks by status, and active incidents. register_check: Create a monitoring check. send_heartbeat: Send a success signal. create_incident: Create a new incident. resolve_incident: Resolve an existing incident.

Q: How do I install IonHour?

Install IonHour by running: npx @ionhour/mcp-server

Add it to Claude Code

Run this in a terminal.

Run in terminal

claude mcp add -e "IONHOUR_API_KEY=${IONHOUR_API_KEY}" ionhour -- npx @ionhour/mcp-server

Required:IONHOUR_API_KEY

README.md

Connect AI assistants to your IonHour uptime monitoring workspace

@ionhour/mcp-server

Connect AI assistants to your IonHour uptime monitoring workspace using the Model Context Protocol.

Quick Start

# Option 1: Interactive login (recommended)
npx @ionhour/mcp-server login

# Option 2: Set your API key manually
export IONHOUR_API_KEY=ionh_your_key_here

# Run the MCP server
npx @ionhour/mcp-server

Setup with AI Assistants

Smithery

npx -y @smithery/cli install @ionhour/mcp-server --client claude

Claude Code

claude mcp add ionhour -- npx @ionhour/mcp-server

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "ionhour": {
      "command": "npx",
      "args": ["@ionhour/mcp-server"],
      "env": {
        "IONHOUR_API_KEY": "ionh_your_key_here"
      }
    }
  }
}

Cursor

Add to your .cursor/mcp.json:

{
  "mcpServers": {
    "ionhour": {
      "command": "npx",
      "args": ["@ionhour/mcp-server"],
      "env": {
        "IONHOUR_API_KEY": "ionh_your_key_here"
      }
    }
  }
}

VS Code (Copilot)

Add to your .vscode/mcp.json:

{
  "servers": {
    "ionhour": {
      "command": "npx",
      "args": ["@ionhour/mcp-server"],
      "env": {
        "IONHOUR_API_KEY": "ionh_your_key_here"
      }
    }
  }
}

Windsurf

Add to your ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "ionhour": {
      "command": "npx",
      "args": ["@ionhour/mcp-server"],
      "env": {
        "IONHOUR_API_KEY": "ionh_your_key_here"
      }
    }
  }
}

Getting an API Key

Go to your IonHour workspace Settings > API Keys
Create a new key with Read & Write or Read Only permission
Copy the key (starts with ionh_)

Available Tools (49)

Workspace

get_workspace - Get workspace details
whoami - Get API key info (workspace, user, permission level)
get_workspace_summary - Overview of projects, checks by status, and active incidents
get_workspace_reliability - Uptime, incident count, and MTTR over N days
list_team_members - List workspace members and roles
send_invitation - Invite users to the workspace

Projects

list_projects / create_project / update_project

Checks (Monitors)

register_check - Create a monitoring check (accepts human-readable intervals like "every 5 minutes" or "hourly")
list_checks / list_checks_by_status / find_check_by_name
get_check_status - Detailed status with recent signals
get_check_uptime - Uptime percentage with daily buckets
pause_check / resume_check
delete_check - Permanently delete a check and its data

Signals (Heartbeats)

send_heartbeat - Send a success signal
send_failure_signal - Report a failure
list_signals - View signal history

Incidents

list_incidents / search_incidents / get_incident
get_incident_timeline - Incident history for a check
create_incident / acknowledge_incident / resolve_incident
add_incident_note

Deployments

create_deployment - Start a deployment window (auto-pauses checks)
end_deployment - End deployment and resume checks
list_deployments

Dependencies

list_dependencies / get_dependency / create_dependency
update_dependency_status
delete_dependency - Delete a dependency

Status Pages

list_status_pages / create_status_page / update_status_page
create_announcement - Post a status update

Alert Channels

list_alert_channels / create_alert_channel / update_alert_channel
delete_alert_channel - Delete a notification channel

Escalation Rules

list_escalation_rules / create_escalation_rule / update_escalation_rule
delete_escalation_rule - Delete an escalation rule

Resources

The server exposes reference data that AI assistants can browse without calling tools:

URI	Description
`ionhour://enums`	All IonHour enums (check statuses, incident states, severities, etc.)
`ionhour://checks/schema`	Check creation schema with field constraints and status lifecycle
`ionhour://help/ping-formats`	Heartbeat integration examples (curl, Node, Python, cron, CI/CD)
`ionhour://tools/catalog`	Catalog of all tools organized by domain with descriptions
`ionhour://guides/workflows`	Common workflow patterns and best practices

Prompts

Pre-built workflow templates that guide AI assistants through multi-step operations:

Prompt	Args	Description
`diagnose_incident`	`incidentId`	Step-by-step incident investigation
`setup_monitoring`	`serviceName`	Guided new-service monitoring setup
`deployment_checklist`	`projectId`	Pre/during/post-deploy workflow
`weekly_reliability_report`	`day

Tools (6)

get_workspaceGet workspace details

get_workspace_summaryOverview of projects, checks by status, and active incidents

register_checkCreate a monitoring check

send_heartbeatSend a success signal

create_incidentCreate a new incident

resolve_incidentResolve an existing incident

Environment Variables

IONHOUR_API_KEYrequiredAPI key from IonHour workspace Settings > API Keys

Configuration

claude_desktop_config.json

{"mcpServers": {"ionhour": {"command": "npx", "args": ["@ionhour/mcp-server"], "env": {"IONHOUR_API_KEY": "ionh_your_key_here"}}}}

Try it

→Give me a summary of my current workspace reliability and active incidents.

→Create a new monitoring check for my production API that runs every 5 minutes.

→Diagnose the current incident for the payment-gateway service.

→Post an announcement to the status page about the ongoing maintenance.

Frequently Asked Questions

What are the key features of IonHour?

Manage projects, monitoring checks, and incident responses via natural language. View reliability metrics including uptime, incident counts, and MTTR. Automate deployment windows to pause and resume monitoring checks. Expose reference data like enums and check schemas to AI assistants. Support for heartbeats and failure signal reporting.

What can I use IonHour for?

Automating incident investigation and resolution workflows. Setting up monitoring for new services directly through AI chat. Generating weekly reliability reports for team stakeholders. Coordinating status page updates during deployment windows.

How do I install IonHour?

Install IonHour by running: npx @ionhour/mcp-server

What MCP clients work with IonHour?

IonHour works with any MCP-compatible client including Claude Desktop, Claude Code, Cursor, and other editors with MCP support.

Turn this server into reusable context

Keep IonHour docs, env vars, and workflow notes in Conare so your agent carries them across sessions.

Need the old visual installer? Open Conare IDE.

Open Conare

View all monitoring servers →