Log inSubmit server
Runhooks logo

Runhooks

Manage Runhooks HTTP schedules, executions, usage, API keys, and failure alerts through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Runhooks

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "runhooks": {
      "command": "npx",
      "args": [
        "-y",
        "@runhooks/mcp"
      ],
      "env": {
        "RUNHOOKS_API_KEY": "YOUR_VALUE_HERE",
        "RUNHOOKS_API_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 18 tools correctly (Today).

Overview

Runhooks MCP server connects AI agents to the Runhooks REST API for creating and managing recurring or one-off HTTP jobs. It runs locally as an npx-launched MCP process, while job and account operations use HTTPS against Runhooks. Agents can create cron or interval schedules, inspect and replay executions, pause jobs, review usage, and configure failure alerts. Reach for Runhooks when an MCP client needs to automate HTTP calls without building direct scheduling API integration.

Use cases

  • Schedule recurring HTTP requests with cron or interval rules
  • Replay failed or historical job executions
  • Pause and resume automated HTTP jobs
  • Review plan usage and scheduling limits
  • Configure alerts for failed job runs

Key features

  • Cron and interval job scheduling
  • One-off and recurring HTTP jobs
  • Job filtering and pagination
  • Execution history and replay
  • Anonymous account provisioning
  • Email, webhook, and Slack failure alerts

Tools18

What Runhooks lets your agent do. Expand a tool for its parameters.

Verified live~2.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

7/7 checks healthy over the last 25d

What it can do

From the 18 tools this server returned when we ran it.

Can delete or modify data · 2Handles credentials · 3Makes network requests · 2Read-only tools · 16
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age33 days
Maintainers1

Observed 2026-11-08 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · @runhooks/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1.5kPackage downloads in the last 30 days.
Last commit8d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed18Callable tools this server registers over MCP.

How Runhooks works

What Runhooks MCP server does

Runhooks MCP server gives an MCP client access to Runhooks HTTP scheduling infrastructure. Agents can create recurring or one-off HTTP jobs, then inspect and manage those jobs through the same interface. Scheduling supports cron and interval patterns.

The tool set also covers the surrounding operational tasks. Agents can list jobs with filters and pagination, retrieve or update an individual job, delete jobs, and pause or resume them. Execution history can be listed, and a previous execution can be replayed. Account tools expose the current identity, API-key rotation, and anonymous account provisioning. Usage information includes plan limits, while alert tools manage failure notifications through email, webhooks, or Slack.

How it works

The package runs locally on the machine where the MCP client launches it. A client starts the server with npx -y @runhooks/mcp; the process then communicates with the Runhooks REST API over HTTPS. There is no hosted MCP process to connect to.

Authentication uses a Runhooks API key. If RUNHOOKS_API_KEY is set, the server uses that value. Without it, an agent can call provision_account to create an anonymous account without an email address. The resulting rh_live_... key is saved locally in ~/.runhooks/mcp.json and reused by later tool calls. The environment variable takes precedence over the saved key.

Setup and configuration

Add the package as a command-based MCP server in the client configuration. A typical entry uses npx as the command and passes -y and @runhooks/mcp as arguments. The API key can be supplied through the server's environment configuration, or account provisioning can be performed from the client after startup.

RUNHOOKS_API_KEY supplies the Runhooks API key and is optional when local key storage is available. RUNHOOKS_API_URL changes the API origin; its default is https://api.runhooks.app. To verify startup independently, run the package with npx -y @runhooks/mcp, optionally setting RUNHOOKS_API_KEY, and confirm that the client can discover its tools.

Tools and capabilities

  • Provision an anonymous account, inspect the current account, or rotate its API key.
  • Create, list, retrieve, update, delete, pause, and resume scheduled jobs.
  • Configure jobs with cron or interval schedules.
  • Review execution history and replay a previous execution.
  • Check plan usage and limits.
  • Create, list, retrieve, update, and delete failure alerts for email, webhook, or Slack destinations.

The package is intended for MCP clients such as Claude Desktop and Cursor, as well as other clients that support MCP server processes.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Runhooks

Runhooks is an MCP server that connects AI agents to the Runhooks HTTP scheduling API. Its tools provision accounts, manage API keys, create and control cron or interval jobs, inspect executions, replay runs, check usage, and manage failure alerts. It runs locally and communicates with Runhooks over HTTPS.

Install Runhooks by adding `npx -y @runhooks/mcp` as a command-based MCP server in your client configuration. Set `RUNHOOKS_API_KEY` in the server environment, or start without it and ask the agent to call `provision_account` once.

Yes, Runhooks works with Cursor. Configure Cursor to launch `npx -y @runhooks/mcp` as an MCP server and provide `RUNHOOKS_API_KEY`, or provision an anonymous account from the client after startup.

Create a scheduled HTTP job by calling the `create_job` tool through the MCP client. The tool supports cron or interval scheduling, after which other tools can list, retrieve, update, pause, resume, or delete the job.

Replay an execution with the `replay_execution` tool. First use `list_executions` to inspect a job's run history and identify the execution to run again.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewRunhooks AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/runhooks?style=directory)](https://allmcps.com/mcp/runhooks)
HTML Embed
<a href="https://allmcps.com/mcp/runhooks"><img src="https://allmcps.com/api/badge/runhooks?style=directory" alt="Runhooks on AllMCPs" /></a>