@runhooks/mcp
Provides tools for managing failure alerts, including sending notifications to Slack channels.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@runhooks/mcpschedule a job to call https://example.com/webhook every hour"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@runhooks/mcp
Model Context Protocol (MCP) server for Runhooks — reliable HTTP scheduling infrastructure. It lets AI agents (Claude Desktop, Cursor, and any MCP client) schedule and manage cron jobs and webhooks directly.
The server runs locally on your machine: your MCP client spawns it with npx and it talks
to the Runhooks REST API over HTTPS. There is no hosted service — just this package.
Install
Add it to your MCP client config. For Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"runhooks": {
"command": "npx",
"args": ["-y", "@runhooks/mcp"],
"env": { "RUNHOOKS_API_KEY": "rh_live_..." }
}
}
}No API key yet? Leave env out and ask the agent to run the provision_account tool — it
creates an instant account (no email) and returns an rh_live_... key. Save that key as
RUNHOOKS_API_KEY and restart your client.
Related MCP server: silentwatch-mcp
Verify
Check the server starts and advertises its tools (replace the key, or omit env and use
provision_account from inside your client):
RUNHOOKS_API_KEY=rh_live_... npx -y @runhooks/mcpEnvironment variables
Variable | Description | Default |
| Your API key ( | — |
| API origin. |
|
Tools
Tool | Description |
| Create an anonymous account and get an API key (no email). |
| Show the current account. |
| Rotate the API key. |
| Create a scheduled job (cron or interval). |
| List jobs with filters and pagination. |
| Get one job by ID. |
| Update a job. |
| Delete a job. |
| Pause or resume a job. |
| List a job's run history. |
| Re-run a past execution. |
| Show plan usage and limits. |
| Manage failure alerts (email, webhook, Slack). |
Links
Documentation: https://runhooks.app/docs/mcp
API reference: https://runhooks.app/docs/api
License
MIT
This server cannot be deployed
Related MCP Connectors
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Open-source Zapier/n8n alternative as an MCP server: agents build, run and debug your workflows.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Build, validate, deploy — HTTP APIs, cron jobs, webhooks and MCP tools — from your AI client.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server for scheduling and executing Claude Code CLI tasks via cron expressions, featuring a web dashboard and webhook support. It enables users to dynamically create custom MCP servers, manage recurring AI jobs, and track execution history with token and cost analytics.24MIT
- AlicenseAqualityAmaintenanceAn MCP server that surfaces scheduled-job state and detects silent failures (exit 0 but no useful output) for cron, systemd timers, and OpenClaw schedulers, enabling AI agents to query job health and overdue status directly.6MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to execute real-world actions through 10 specialized engines covering authenticated API calls, browser automation, visual QA, shell commands, file operations, job scraping, and parallel task execution.-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets AI agents manage cron jobs through natural language — adding, listing, pausing, removing, running, and viewing logs of scheduled jobs with plain-English schedule parsing, automatic log capture, missed-run detection, and failure alerts.MIT