Hooksense MCP Server

Model Context Protocol server for HookSense — the webhook & callback layer for AI agents. Lets Claude Desktop, Cursor, Claude Code, Continue, and any MCP client create a callback URL, wait for the…

Local serverstdioMIT

What is the Hooksense MCP Server?

hooksense-mcp is an MCP project maintained in the ozers/hooksense-mcp repository. The maintainer describes its purpose as “Model Context Protocol server for HookSense — the webhook & callback layer for AI agents. Lets Claude Desktop, Cursor, Claude Code, Continue, and any MCP…”. Read the project documentation for the complete scope.

Installation

The documented npm package is @hooksense/mcp. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.

Configuration values

The example declares HOOKSENSE_TOKEN. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.

Source

Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
create_callback_endpointCreate a callback endpoint; returns the callbackUrl
wait_for_callbackBlock until the next callback lands, then return it (timeoutMs, after cursor)
list_callbacksList captured callbacks, including bodies and metadata
get_callback_payloadFetch one callback with full headers + decrypted body
verify_signatureTiming-safe HMAC check against the endpoint's configured secret
replay_callbackReplay a callback to a public HTTP(S) URL from the HookSense server
list_endpointsList your endpoints
get_endpointGet one endpoint's full settings

How to install the Hooksense MCP Server

{
  "mcpServers": {
    "hooksense": {
      "command": "npx",
      "args": [
        "-y",
        "@hooksense/mcp"
      ],
      "env": {
        "HOOKSENSE_TOKEN": "YOUR_HOOKSENSE_TOKEN"
      }
    }
  }
}

From the project documentation. Replace placeholders and example paths before connecting.

Configuration

VariableDescriptionRequired
HOOKSENSE_TOKENDeclared in the maintainer’s client configuration.Yes