Enterprise DNA
M MCP Servers Developer low

getnahook/nahook-mcp

by Various

The official Model Context Protocol server for Nahook — trigger webhooks, inspect deliveries, and debug failures from Claude Desktop, Cursor, Cline, and any MCP-compatible AI clien

G

MCP

getnahook/nahook-mcp

Added 18 June 2026

#ai-tools #claude #cursor #developer-tools #mcp #mcp-server #model-context-protocol #webhooks

Overview

The official Model Context Protocol server for Nahook. It lets MCP-compatible AI clients like Claude Desktop, Cursor, and Cline trigger webhooks, inspect delivery logs, and debug failures directly from the chat interface.

Best for

Best for
Developers using MCP-compatible AI assistants who need to trigger and debug webhook deliveries

Use cases

  • Trigger webhook deliveries from an AI assistant without leaving the chat
  • Inspect delivery logs and debug failed webhook calls in real time
  • Integrate webhook-based workflows into MCP-compatible development tools

Notes

The official Model Context Protocol server for Nahook. It lets MCP-compatible AI clients like Claude Desktop, Cursor, and Cline trigger webhooks, inspect delivery logs, and debug failures directly from the chat interface.

0 stars on GitHub. Last updated 2026-06-17. Licensed MIT.

Use cases

  • Trigger webhook deliveries from an AI assistant without leaving the chat
  • Inspect delivery logs and debug failed webhook calls in real time
  • Integrate webhook-based workflows into MCP-compatible development tools

Pros

  • Works with multiple MCP-compatible clients out of the box
  • Provides direct visibility into webhook delivery and failure details
  • Lightweight setup with no extra infrastructure required

Cons

  • Requires an existing Nahook account and webhook configuration
  • Limited to debugging and triggering webhooks, no broader automation
  • No built-in support for non-MCP clients or custom protocols

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Works with multiple MCP-compatible clients out of the box
  • Provides direct visibility into webhook delivery and failure details
  • Lightweight setup with no extra infrastructure required

Cons

  • Requires an existing Nahook account and webhook configuration
  • Limited to debugging and triggering webhooks, no broader automation
  • No built-in support for non-MCP clients or custom protocols