Manage Webhooks from Claude, ChatGPT & Any AI Agent
The Hookbase MCP server exposes 123 tools — sources, destinations, routes, transforms, alerts, cron jobs, tunnels, analytics, and the whole outbound webhooks stack — so your AI assistant can inspect, debug, and configure your webhook infrastructure by conversation instead of clicking.
Local Process or Hosted URL
Clients that can spawn a local process — Claude Desktop, Cursor, and most desktop MCP clients — run the server over stdio with a single npx command. Everything else connects to the hosted Streamable HTTP endpoint. Same 123 tools either way.
- No install for the hosted endpoint — just a URL
- Authenticate with your existing Hookbase API key
- Organization resolved automatically from the key
- Stateless HTTP transport — nothing to keep running
npx @hookbase/mcp-server{
"mcpServers": {
"hookbase": {
"command": "npx",
"args": ["-y", "@hookbase/mcp-server"],
"env": {
"HOOKBASE_API_KEY": "whr_live_your_key_here"
}
}
}
}What the MCP Server Gives Your Agent
Tools, resources, and prompts covering nearly the entire Hookbase product — not a read-only preview.
123 Tools Across the Whole Product
Sources, destinations, routes, transforms, schemas, filters, alert rules, cron jobs, tunnels, analytics, audit logs, redaction policies, and the full outbound webhooks stack — all callable as MCP tools.
Local stdio Transport
Run `npx @hookbase/mcp-server` as a local process for clients that can spawn one, like Claude Desktop and Cursor. Your API key stays in the client config on your machine.
Hosted Remote Endpoint
Clients that cannot spawn a local process just point at https://mcp.hookbase.app/mcp — a stateless Streamable HTTP endpoint with the same tools. No install, no runtime to manage.
Read-Only MCP Resources
Stable URIs an agent can fetch directly instead of guessing: hookbase://sources/{id}/ingest-url for a source ingest URL and hookbase://tunnels/{id}/ws-url for a tunnel WebSocket URL.
Prompts That Show the Way
The server ships example prompts for common jobs — listing sources, checking success rates, replaying failures, provisioning outbound endpoints — so agents pick the right tool on the first try.
Scoped to Your API Key
Auth is a standard whr_ Hookbase API key. The organization is resolved from the key, so the agent can only reach what that key can reach. Revoke it and access stops immediately.
What You Can Do
The kinds of tasks that take a dozen clicks in a dashboard and one sentence in a chat.
Debug a Failed Delivery
Skip the dashboard filtering. Ask your agent to pull recent failures for a source and tell you what they have in common — status codes, response bodies, timing.
Provision Infrastructure Conversationally
Describe what you need in plain English and let the agent create the pieces with the right IDs wired together, then confirm the result back to you.
Bulk-Replay a Failure Cluster
When one downstream outage takes out a batch of deliveries, have the agent scope the blast radius and replay the whole cluster in one step.
Answer Questions About Your Traffic
Analytics, event history, and audit logs are all tools, so an agent can answer operational questions without you writing a query or opening a chart.
Why Connect Hookbase to an AI Agent?
Point Your Agent at Hookbase
Create an account, generate an API key, and connect in under a minute. Free tier included — no credit card required.