IonHour MCP Server
Connects AI assistants to IonHour uptime monitoring workspaces to manage projects, monitoring checks, and incident responses. It enables users to view reliability metrics, send heartbeats, and manage status pages through natural language.
README
@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
Workspace
get_workspace- Get workspace detailsget_workspace_summary- Overview of projects, checks, and incidentsget_workspace_reliability- Uptime, incident count, and MTTR metricslist_team_members- List workspace members and rolessend_invitation- Invite users to the workspace
Projects
list_projects/create_project/update_project
Checks (Monitors)
register_check- Create a new monitoring checklist_checks/list_checks_by_status/find_check_by_nameget_check_status- Detailed status with recent signalsget_check_uptime- Uptime percentage with daily bucketspause_check/resume_check
Signals (Heartbeats)
send_heartbeat- Send a success signalsend_failure_signal- Report a failurelist_signals- View signal history
Incidents
list_incidents/search_incidents/get_incidentget_incident_timeline- Incident history for a checkcreate_incident/acknowledge_incident/resolve_incidentadd_incident_note
Deployments
create_deployment- Start a deployment window (auto-pauses checks)end_deployment- End deployment and resume checkslist_deployments
Dependencies
list_dependencies/get_dependency/create_dependencyupdate_dependency_status
Status Pages & Alerts
list_status_pages/create_status_page/update_status_pagecreate_announcementlist_alert_channels/create_alert_channel/update_alert_channellist_escalation_rules/create_escalation_rule/update_escalation_rule
CLI Commands
npx @ionhour/mcp-server [command] [options]
Commands:
(default) Start the MCP server
login Authenticate via browser and store API key
logout Remove stored credentials
whoami Show current authentication status
Options:
--api-key KEY IonHour API key (or set IONHOUR_API_KEY env var)
--base-url URL MCP base URL (default: https://mcp.ionhour.com)
--version, -v Show version
--help, -h Show help
login
Opens your browser to authenticate with IonHour, then automatically creates and stores an API key:
npx @ionhour/mcp-server login
Credentials are stored at ~/.config/ionhour/credentials.json (file permissions: 600).
After login, you can run the MCP server without setting IONHOUR_API_KEY.
How It Works
This package runs a local MCP server over stdio that proxies requests to the IonHour API. Your AI assistant communicates with this local server, which forwards tool calls to your IonHour workspace.
AI Assistant <--stdio--> @ionhour/mcp-server <--HTTPS--> IonHour API
Requirements
- Node.js >= 18
- An IonHour account with an API key
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.