MCP Server

The Hookbase MCP (Model Context Protocol) server lets you manage webhooks directly from AI assistants like Claude. Ask Claude to list your sources, replay failed deliveries, check analytics, and more.

What is MCP?

Model Context Protocol is an open standard that allows AI assistants to interact with external tools and services. The Hookbase MCP server exposes 24 tools for managing your webhook infrastructure.

Quick Start

1. Get your API key

Get your API key from the Hookbase dashboard under Settings → API Keys.

2. Configure Claude Desktop

Add to your Claude Desktop configuration file:

macOS

// ~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "hookbase": {
      "command": "npx",
      "args": ["-y", "@hookbase/mcp-server"],
      "env": {
        "HOOKBASE_API_KEY": "whr_live_your_key_here"
      }
    }
  }
}

Linux

// ~/.config/claude/claude_desktop_config.json
{
  "mcpServers": {
    "hookbase": {
      "command": "npx",
      "args": ["-y", "@hookbase/mcp-server"],
      "env": {
        "HOOKBASE_API_KEY": "whr_live_your_key_here"
      }
    }
  }
}

Windows

// %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "hookbase": {
      "command": "npx",
      "args": ["-y", "@hookbase/mcp-server"],
      "env": {
        "HOOKBASE_API_KEY": "whr_live_your_key_here"
      }
    }
  }
}

3. Restart Claude Desktop

Restart Claude Desktop to load the MCP server. You'll see "hookbase" in the available tools.

4. Start chatting!

You can now ask Claude to manage your webhooks:

• "List all my webhook sources"
• "Show me failed deliveries from the last hour"
• "What's my success rate for the last 24 hours?"
• "Replay the failed deliveries for my Slack destination"

Example Conversations

Debugging failed webhooks

You: Show me recent failed deliveries

Claude: I found 3 failed deliveries in the last hour:

• del_abc123 to Slack (status: 500, error: "Internal Server Error")
• del_def456 to CI/CD (status: timeout)
• del_ghi789 to Analytics (status: 401, error: "Unauthorized")

You: Replay the Slack one

Claude: Successfully replayed delivery del_abc123. New status: success (200 OK, 145ms)

Creating a new webhook flow

You: Create a source for GitHub webhooks and route them to my build server at https://build.example.com/webhook

Claude: Done! I've created:

• Source: "GitHub" (slug: github, provider: github)
• Destination: "Build Server" (url: https://build.example.com/webhook)
• Route: "GitHub → Build Server"

Your webhook URL is: https://api.hookbase.app/ingest/your-org/github

Checking analytics

You: What's my webhook performance this week?

Claude: Here's your 7-day analytics:

• Total events: 12,847
• Total deliveries: 25,691
• Success rate: 99.2%
• Average response time: 234ms

Top sources: GitHub (8,234 events), Stripe (3,102 events) Top destinations: Slack (15,234 deliveries, 99.8% success)

Available Tools

The MCP server provides 24 tools organized by category:

Category	Tools	Description
Sources	4	List, get, create, update webhook sources
Destinations	4	List, get, create, test destinations
Routes	3	List, get, create routes
Events	3	List, get events, generate debug cURL
Deliveries	4	List, get, replay, bulk replay deliveries
Tunnels	3	List, create, check status of tunnels
Cron	2	List cron jobs, trigger manually
Analytics	1	Get dashboard metrics

See Tools Reference for complete documentation.

Configuration

Variable	Required	Description
HOOKBASE_API_KEY	Yes	Your Hookbase API key
HOOKBASE_ORG_ID	No	Organization ID (only needed with multiple orgs)
HOOKBASE_API_URL	No	API URL override

The organization is automatically detected from your API key.

Alternative Installation

Global install

npm install -g @hookbase/mcp-server

Then use hookbase-mcp as the command:

{
  "mcpServers": {
    "hookbase": {
      "command": "hookbase-mcp",
      "env": {
        "HOOKBASE_API_KEY": "whr_live_your_key_here"
      }
    }
  }
}

From source

git clone https://github.com/hookbase/hookbase.git
cd hookbase/mcp-server
npm install && npm run build

Troubleshooting

Server not appearing in Claude

1. Verify the config file path is correct for your OS
2. Ensure the JSON is valid (no trailing commas)
3. Restart Claude Desktop completely (quit and reopen)

"Missing HOOKBASE_API_KEY"

Make sure your API key is set in the env section of your config.

"Invalid API key"

Check that your API key:

• Starts with whr_
• Is not expired
• Has not been revoked

"Multiple organizations found"

If you belong to multiple organizations, add HOOKBASE_ORG_ID to your env:

{
  "env": {
    "HOOKBASE_API_KEY": "whr_live_xxx",
    "HOOKBASE_ORG_ID": "org_xxx"
  }
}

Next Steps

• Tools Reference - Complete tool documentation
• CLI Overview - Command-line interface
• API Reference - REST API documentation