Hooklaw banner
lucianfialho lucianfialho

Hooklaw

AI community

Description

Webhook orchestrator with AI agents and native MCP tools. Recipes connect any webhook to any MCP server. BYOK, self-hosted.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

HookLaw

HookLaw

Event-driven AI agents with native MCP tools.

Webhooks & RSS feeds in. MCP tools out. AI agent in the middle.

License TypeScript Tests MCP Native


Watch the onboarding demo

  Stripe webhook  ──→  Recipe  ──→  QuickBooks MCP (create invoice)
  GitHub webhook  ──→  Recipe  ──→  Slack MCP (post message)
  HN RSS feed     ──→  Recipe  ──→  Slack MCP (daily digest)
  Any event       ──→  Recipe  ──→  Any MCP server

HookLaw connects **any event source** (webhooks, RSS/Atom feeds) to **any MCP server** through AI agents. Define recipes in YAML, bring your own API keys, self-host it.

Why HookLaw

Other platforms treat webhooks as just another input channel for their AI assistant. HookLaw is **event-first**: every event source gets its own AI agent and MCP tool connections.

  • Proactive, not just reactive — RSS feeds let your agents monitor the world and act on new information automatically
  • Multi-agent chains — recipes trigger other recipes on success/error with depth tracking
  • Human-in-the-loop — agents pause for approval before taking action
  • Agent memory — conversation context persists across executions
  • **Condition