MCP Server
Connect AI agents to HookWatch via the Model Context Protocol. Manage webhook endpoints, retry failed events, create cron jobs, and configure alerts — all from your AI coding assistant.
How It Works
The MCP server acts as a bridge between AI agents and the HookWatch platform. It connects to the HookWatch core via gRPC and exposes 34 tools that agents can call.
AI Agent (Claude Code, Cursor, Windsurf, etc.)
| MCP Protocol (stdio or HTTP)
v
HookWatch MCP Server
| gRPC (authenticated with your API key)
v
HookWatch Core APITwo transport modes are supported:
- stdio — runs locally as a subprocess of your AI tool (recommended for development)
- HTTP — hosted server at
mcp.hookwatch.dev(no local install needed)
Setup
Step 1: Create an API Key
Go to the HookWatch Dashboard → API Keys → Create Key. Give it a name like mcp-server and copy the key.
Store your key securely
The full API key is only shown once. If you lose it, create a new one.
Step 2: Connect Your AI Tool
Claude Code
Option A: Local binary (stdio)
Option B: Hosted server (HTTP — no install needed)
Cursor
Option A: Local binary (stdio)
Option B: Hosted server (HTTP)
Other MCP Clients
Any MCP-compatible client can connect via HTTP. Use the endpoint https://mcp.hookwatch.dev/mcp with an Authorization: Bearer hk_... header.
Install Binary (Optional)
Only needed for stdio mode. If you use the hosted HTTP server, skip this step.
Also available for macOS (darwin_arm64, darwin_amd64) and Windows (windows_amd64.zip).
Self-Host with Docker
Run your own MCP server instance. Clients authenticate with their own API keys via the Authorization header — no server-wide key needed.
The server exposes /mcp (MCP endpoint) and /health (health check) on port 8085.
Available Tools
34 tools across 7 categories:
Endpoints
| Tool | Description |
|---|---|
list_endpoints | List all webhook endpoints with stats |
get_endpoint | Get endpoint details, retry and signature config |
create_endpoint | Create a new webhook endpoint |
update_endpoint | Update name, URL, active status, or retry config |
delete_endpoint | Delete an endpoint and its events |
Events
| Tool | Description |
|---|---|
list_events | List events with status, endpoint, and pagination filters |
get_event | Get full event details (headers, body, response) |
get_event_metrics | Aggregated delivery metrics with daily breakdown |
count_events | Count events by endpoint or status |
retry_event | Re-deliver a failed event |
replay_event | Replay with optional modified body/headers |
delete_event | Delete an event |
Alerts
| Tool | Description |
|---|---|
list_alerts | List all alert configurations |
get_alert | Get alert details |
get_alerts_by_resource | Find all alerts for an endpoint or cron job |
create_alert | Create alert (Slack, Discord, email, Telegram) |
update_alert | Update alert target, type, or template |
delete_alert | Delete an alert |
Cron Jobs
| Tool | Description |
|---|---|
list_cron_jobs | List all cron jobs |
get_cron_job | Get cron job details |
create_cron_job | Create a new cron job |
update_cron_job | Update schedule, command, or config |
delete_cron_job | Delete a cron job |
enable_cron_job | Enable a disabled job |
disable_cron_job | Disable a job |
run_cron_job | Trigger manual execution |
list_cron_executions | Execution history with filters |
get_cron_execution | Execution details (stdout, stderr, exit code) |
retry_cron_execution | Retry a failed execution |
list_agents | List registered CLI agents |
Teams, WebSocket & API Keys
| Tool | Description |
|---|---|
list_teams | List your teams |
get_team | Get team details |
list_team_members | List team members |
list_ws_endpoints | List WebSocket proxy endpoints |
get_ws_endpoint | Get WebSocket endpoint details |
list_ws_connections | List active WebSocket connections |
list_api_keys | List API keys (values hidden) |
create_api_key | Create a new API key |
delete_api_key | Delete an API key |
Examples
Once connected, your AI agent can call any tool. Here are some common workflows:
List your endpoints
Create an endpoint
Retry a failed event
Open Source
The MCP server is open source at github.com/hookwatch-dev/mcp-server. Contributions are welcome.