Nahook Mcp

What is Nahook Mcp?

The official Model Context Protocol server for Nahook, enabling MCP-compatible AI assistants like Claude Desktop, Cursor, Cline, and Zed to drive webhook deliveries, endpoints, and event triggers.

How to use Nahook Mcp?

Install the nahook CLI via Homebrew (brew install getnahook/tap/nahook) or a curl script, run nahook login to authenticate, then configure your MCP client with {"mcpServers":{"nahook":{"command":"nahook","args":["mcp","serve"]}}}.

Key features of Nahook Mcp

• Trigger an event and fan it out to every subscribed endpoint
• Send a webhook directly to one endpoint
• Inspect endpoints, deliveries, and per-attempt logs
• Retry failed or dead-lettered deliveries
• Manage endpoints (create, update, pause, resume — never delete)
• Write tools include destructiveHint/readOnlyHint for safety

Use cases of Nahook Mcp

• Debug webhook delivery failures with detailed logs
• Retry undelivered webhooks from your AI assistant
• Create or update endpoints without leaving your coding environment
• Trigger event notifications to multiple services in one action

FAQ from Nahook Mcp

What distinguishes Nahook Mcp from other MCP servers?

Nahook Mcp is the official MCP server for Nahook, designed specifically for managing webhook endpoints, deliveries, and event triggers from AI assistants.

What are the dependencies to run Nahook Mcp?

You need the nahook CLI installed (via Homebrew or the install script) and an active nahook login session.

Where does data live?

The README does not specify where data is stored; it interacts with the Nahook service remotely.

What are the known limits?

The server intentionally never deletes endpoints by design — you can only create, update, pause, or resume them.

What transport or authentication does it use?

The server runs as a subcommand of the nahook CLI over stdio, and authentication is done via nahook login (the README does not detail the underlying auth mechanism).