Runhooks

io.github.runhooksv0.1.3Updated Oct 8, 2026

Schedule and manage cron jobs and webhooks on Runhooks from your AI agent.

VerifiedSTDIODesktop onlyDeveloper ToolsCloud & Infrastructure

Overview

AI-generated overview

Lets an assistant create and manage Runhooks cron jobs, webhooks, run history, and failure alerts through the Runhooks API.

What it does
This local MCP server connects an assistant to Runhooks scheduling infrastructure. It exposes tools to create, list, get, update, delete, pause, and resume scheduled jobs (cron or interval), inspect a job's execution history, replay a past execution, check plan usage and limits, and manage failure alerts over email, webhook, or Slack. It can also provision an anonymous account, show the current account, and rotate the API key.
When to use it
Worth adding when you want an assistant to set up or maintain scheduled HTTP calls and webhooks, review or replay past runs, or configure failure alerts without leaving the chat. It is aimed at developers already using or evaluating Runhooks as scheduling infrastructure.
Requirements
Runs locally as an npm package (@runhooks/mcp) spawned by an MCP client such as Claude Desktop or Cursor, so Node.js and npx are needed. It talks to the Runhooks REST API over HTTPS. The RUNHOOKS_API_KEY environment variable is required for all tools except provision_account; RUNHOOKS_API_URL optionally overrides the API origin. Desktop only.
Before you install
The server handles a live API key (RUNHOOKS_API_KEY, rh_live_...), which grants access to the account and its jobs; provision_account creates an account without email, and rotate_key invalidates the previous key. Tools can create, update, delete, pause, resume, and replay jobs and alerts, so changes affect real scheduled HTTP calls. Job definitions and alert settings are sent to the Runhooks API.

Installation

In SourceWeft

  1. Open Runhooks in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@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):

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.

Verify

Check the server starts and advertises its tools (replace the key, or omit env and use provision_account from inside your client):

bash
RUNHOOKS_API_KEY=rh_live_... npx -y @runhooks/mcp

Environment variables

VariableDescriptionDefault
RUNHOOKS_API_KEYYour API key (rh_live_...). Required for all tools except provision_account.—
RUNHOOKS_API_URLAPI origin.https://api.runhooks.app

Tools

ToolDescription
provision_accountCreate an anonymous account and get an API key (no email).
whoamiShow the current account.
rotate_keyRotate the API key.
create_jobCreate a scheduled job (cron or interval).
list_jobsList jobs with filters and pagination.
get_jobGet one job by ID.
update_jobUpdate a job.
delete_jobDelete a job.
pause_job / resume_jobPause or resume a job.
list_executionsList a job's run history.
replay_executionRe-run a past execution.
get_usageShow plan usage and limits.
list_alerts / create_alert / get_alert / update_alert / delete_alertManage failure alerts (email, webhook, Slack).

Links

License

MIT

Source: README.md at commit d9ff52d

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.1.3LatestOct 8, 2026