Anyhook MCP

What gba3124/anyhook-mcp does

gba3124/anyhook-mcp exposes AnyHook webhook operations as MCP tools for coding agents. It supports the full workflow from creating an inbound endpoint to examining received events and retrying failed deliveries. Agents can also generate provider-shaped requests, validate signatures, and configure isolated handlers that run on incoming events.

AnyHook apps receive webhook traffic at an inbound URL. An app can log events without destinations, forward them to configured destinations, or run a deployed handler in AnyHook's sandbox. The server supports provider-specific behavior for Stripe, GitHub, Shopify, Slack, LINE, Discord, Linear, Vercel, Paddle, HubSpot, PayPal, and Xero where applicable to the exposed tools.

How it works

The anyhook_quickstart tool creates an ephemeral relay endpoint and API key without signup. The endpoint works immediately, can be claimed through the returned URL, and expires after seven days if it remains unclaimed. A connected session can then use remote AnyHook tools against that account. For local development, npx -y anyhook-mcp listen 3000 prints a public webhook URL and forwards incoming webhook bytes to port 3000.

Agents can create an app directly or use anyhook_connect with a Stripe or GitHub key. The connect operation registers the app's inbound URL with the provider, stores the resulting signing secret, and enables edge verification; the provider key is used once. Events can be listed in summary form, inspected individually for headers and bodies, and replayed to destinations. Failed or still-retrying events can be filtered or replayed in bulk.

Setup and configuration

Run the MCP package locally with a standard MCP configuration:

{
  "mcpServers": {
    "anyhook": {
      "command": "npx",
      "args": ["-y", "anyhook-mcp"]
    }
  }
}

The package requires Node.js 20 or later for development. An existing AnyHook account can be connected through the hosted MCP endpoint at https://anyhook.net/mcp, with sign-in completed in a browser. Alternatively, start with the local package and call anyhook_quickstart.

Tools and capabilities

• Create and list apps, inbound URLs, provider sources, and destinations.
• Receive email as events through an app-specific anyhook.net address.
• List event summaries and inspect one event's complete inbound and destination data.
• Mock signed Stripe, GitHub, or Slack requests, or insert mocks into the local event store.
• Verify signatures for supported webhook providers.
• Replay individual events or retry every failed event for an app.
• Deploy and test sandboxed event handlers, including scheduled handlers on eligible plans.

Limitations and notes

Event listings contain summaries; use inspection to retrieve request headers and bodies. Payloads may contain personal data, so the server's per-event inspection workflow avoids fetching full bodies for every result. Replays execute the destination again, so non-idempotent receivers may process an event twice.

Mock insertion with anyhook_simulate is available only in local mode; remote mode uses a real inbound URL instead. Apps without destinations still log events but deliver them nowhere, while inactive apps acknowledge POST requests and discard them. Code runs, tests, retries, and schedule firings count against the applicable monthly run limit, and replay use is subject to plan limits.