Ionhour MCP Server -- connect AI assistants to your uptime monitoring workspace
Connect MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Ionhour MCP Server -- connect AI assistants to your uptime monitoring workspace. The mcp mcp server is what makes that connection.
ionh_)The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Smithery — The Smithery tool exposed by this serverCursor — The Cursor tool exposed by this serverWindsurf — The Windsurf tool exposed by this serverWorkspace — The Workspace tool exposed by this serverProjects — The Projects tool exposed by this serverIncidents — The Incidents tool exposed by this serverDeployments — The Deployments tool exposed by this serverDependencies — The Dependencies tool exposed by this serversetup — Interactive wizard that detects installed editors (Cursor, Claude Desktop, VS Code, Claude Code, Windsurf) and writes the Ionhour MCP serverlogin — Opens your browser to authenticate with Ionhour, then automatically creates and stores an API key:logout — Removes stored credentials from ~/.config/ionhour/credentials.json:whoami — Shows the current authentication status — the workspace, user, and permission level associated with the stored API key:Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: IONHOUR_API_KEY, IONHOUR_BASE_URL, IONHOUR_AUTH_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — Smithery, Cursor, Windsurf and 9 more — is a fair guide to whether it matches your workflow. It is maintained by ionhour; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Smithery | The Smithery tool exposed by this server. |
| Cursor | The Cursor tool exposed by this server. |
| Windsurf | The Windsurf tool exposed by this server. |
| Workspace | The Workspace tool exposed by this server. |
| Projects | The Projects tool exposed by this server. |
| Incidents | The Incidents tool exposed by this server. |
| Deployments | The Deployments tool exposed by this server. |
| Dependencies | The Dependencies tool exposed by this server. |
| setup | Interactive wizard that detects installed editors (Cursor, Claude Desktop, VS Code, Claude Code, Windsurf) and writes the Ionhour MCP server configuration into each one. Prompts for login if no credentials are stored: |
| login | Opens your browser to authenticate with Ionhour, then automatically creates and stores an API key: |
| logout | Removes stored credentials from ~/.config/ionhour/credentials.json: |
| whoami | Shows the current authentication status — the workspace, user, and permission level associated with the stored API key: |
{
"mcpServers": {
"ionhour": {
"command": "npx",
"args": ["@ionhour/mcp-server"],
"env": {
"IONHOUR_API_KEY": "ionh_your_key_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| IONHOUR_API_KEY | Credential the server authenticates with. | Yes |
| IONHOUR_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| IONHOUR_AUTH_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.