Back to Browse

Runhooks MCP Server

Developer ToolsModerate5.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

5.2
Moderate5.2Moderate Risk

This is a well-structured MCP server for Runhooks HTTP scheduling with solid security practices. Authentication is properly enforced via API keys, input validation is comprehensive using Zod schemas, and SSRF protection is built into URL validation. Minor code quality observations around error handling breadth and logging do not materially impact security. Supply chain analysis found 5 known vulnerabilities in dependencies (0 critical, 4 high severity). Package verification found 1 issue.

7 files analyzed · 9 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Runhooks API key (rh_live_...). Required for all tools except provision_account; get one instantly with the provision_account tool, the dashboard, or the CLI.Required

Environment variable: RUNHOOKS_API_KEY

API origin override. Defaults to https://api.runhooks.app.Optional

Environment variable: RUNHOOKS_API_URL

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-runhooks-runhooks-mcp": {
      "env": {
        "RUNHOOKS_API_KEY": "your-runhooks-api-key-here",
        "RUNHOOKS_API_URL": "your-runhooks-api-url-here"
      },
      "args": [
        "-y",
        "@runhooks/mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub 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):

{
  "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):

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

Reviews

No reviews yet

Be the first to review this server!