@stackcurious/hookdeck-mcp
v0.1.0
Published
MCP server for Hookdeck — give your AI agent control of webhook events, attempts, sources, destinations, and connections. Debug failed deliveries, retry events, inspect issues — all from inside Claude or Cursor.
Maintainers
Readme
@stackcurious/hookdeck-mcp
MCP server for Hookdeck. Gives your AI agent (Claude, Cursor, Copilot) direct control of webhook events, attempts, sources, destinations, and connections — so debugging a failed delivery becomes a conversation, not a dashboard hunt.
Built and maintained by Q, an autonomous agent for shipping dev-tool integrations.
Why this exists
Hookdeck is the event gateway for webhooks. When a webhook fails, the diagnostic loop is: (1) find the event, (2) inspect the request/response, (3) check delivery attempts, (4) decide whether to retry. That loop is faster as an MCP than as a dashboard click-through, especially when an agent is already in your editor.
This MCP exposes 12 tools covering the most common debugging and triage flows:
hookdeck_list_events— find recent events, filter by status/connection/source/destination/response codehookdeck_get_event— full event detail including request body and all attemptshookdeck_retry_event— manually retry one eventhookdeck_list_attempts— see retry history per eventhookdeck_get_attempt— drill into one delivery attempthookdeck_list_connections— map the source → destination topologyhookdeck_get_connection— full connection detail including ruleset and transformationhookdeck_list_sources— list webhook receivershookdeck_list_destinations— list webhook delivery targetshookdeck_list_issues— triage open delivery problemshookdeck_dismiss_issue— mark an issue IGNOREDhookdeck_trigger_bookmark— replay a bookmarked event
Install
npm install -g @stackcurious/hookdeck-mcp
# or use directly via npxConfigure
Set HOOKDECK_API_KEY to your Hookdeck API key. Find it at dashboard.hookdeck.com → Settings → API Keys.
export HOOKDECK_API_KEY=hd_xxxOptional environment variables:
HOOKDECK_API_VERSION— API version segment (default:2025-07-01)HOOKDECK_API_BASE— API base URL (default:https://api.hookdeck.com)
Wire to Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"hookdeck": {
"command": "npx",
"args": ["-y", "@stackcurious/hookdeck-mcp"],
"env": {
"HOOKDECK_API_KEY": "hd_xxx"
}
}
}
}Restart Claude Desktop. The 12 hookdeck tools will appear in the tool tray.
Wire to Cursor
Add to ~/.cursor/mcp.json (or project .cursor/mcp.json):
{
"mcpServers": {
"hookdeck": {
"command": "npx",
"args": ["-y", "@stackcurious/hookdeck-mcp"],
"env": {
"HOOKDECK_API_KEY": "hd_xxx"
}
}
}
}Example prompts
Once wired, your agent can answer questions like:
- "Show me failed events from the last hour."
- "What's the response body on event evt_abc123?"
- "Retry the last 5 failed deliveries to my Stripe destination."
- "Are there any open issues on the Shopify-orders connection?"
- "Trigger bookmark wbk_xyz again — I want to test the new transformation."
Local development
git clone https://github.com/stackcurious/hookdeck-mcp
cd hookdeck-mcp
npm install
npm run build
HOOKDECK_API_KEY=hd_xxx node dist/index.jsThe server speaks MCP over stdio, so the easiest way to test is to wire it into Claude Desktop or Cursor and then issue prompts.
Hookdeck account setup
This MCP requires a Hookdeck account and a project-scoped API key. Sign up at hookdeck.com — free tier covers up to 100K events/month, which is plenty for evaluation.
License
MIT.
Author
Built by Q, the autonomous agent operated by Dave Oakley. If you're a dev-tool company that wants Q to build an MCP, migration guide, or integration benchmark for your platform, reach out.
