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 result instead of polling, and verify its signature - all from the agent session. Its 8 documented tools cover callback, endpoint. It runs locally over stdio via the published package.

People connecting automation tools to Claude, Cursor, VS Code, or another MCP client. The project is written in JavaScript.

VERIFIED ACTIVE

LAST COMMIT 2026-07-06 · ★ 2 · #142 OF 194 MAINTAINED AUTOMATION · VERIFIED 2026-08-25

MIT · JavaScript servers · how we verify → /methodology

01 · Install Hooksense

before you install - you'll need

HOOKSENSE_TOKEN

Environment variables documented in the project's README - it lists which are required and which have defaults.

Claude Code

claude mcp add ozers-hooksense-mcp -- npx -y @hooksense/mcp

Claude Desktop / Cursor / VS Code - add to config

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

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license MIT - declared in the repository

npm package @hooksense/mcp - the @hooksense scope differs from the repo owner (ozers); confirm it's the project's official package

registry namespace io.github.ozers is GitHub-verified and matches the repo owner

03 · What Hooksense can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

What you can build

With this server connected, an agent can create a callback endpoint, list callbacks received by an endpoint (summary view), fetch one callback with full headers + decrypted body, and post a received callback to any target URL.

Capability map

Tools grouped from the project's README - what Hooksense lets an agent do.

read & search

4 tools - e.g. List callbacks received by an endpoint (summary view); Fetch one callback with full headers + decrypted body; List your endpoints

list_callbacks · get_callback_payload · list_endpoints · get_endpoint

create & write

1 tool - e.g. Create a callback endpoint; returns the callbackUrl

create_callback_endpoint

Wait

1 tool - e.g. Block until the next callback lands, then return it (timeoutMs, after cursor)

wait_for_callback

Verify

1 tool - e.g. Timing-safe HMAC check against the endpoint's configured secret

verify_signature

Replay

1 tool - e.g. POST a received callback to any target URL

replay_callback

04 · Who maintains Hooksense

hooksense is maintained by ozers. It's the only MCP server we track from this author; the repo dates to Jun 2026.

05 · Facts

category
automation - ranked #142 of 194 actively-maintained automation servers as of 2026-08-25.
registry
io.github.ozers/hooksense (active, first published 2026-06-20 · 2 versions)
packages
npm:@hooksense/mcp

06 · Hooksense FAQ

Is Hooksense still maintained?

Yes - as of 2026-08-25, its last commit was 2026-07-06. We re-verify nightly.

What can Hooksense do?

With this server connected, an agent can create a callback endpoint, list callbacks received by an endpoint (summary view), fetch one callback with full headers + decrypted body, and post a received callback to any target URL.

How do I install Hooksense?

Run `npx -y @hooksense/mcp`. The README documents one environment variable (HOOKSENSE_TOKEN) to set first. You can also paste the ready-made client config above.

Does Hooksense run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Hooksense