Koskamo

AnyHook MCP MCP server

AnyHook provides an MCP server that allows AI agents to manage webhook infrastructure. Agents can set up webhook endpoints, monitor incoming events, check for undelivered messages, and replay failed events to ensure reliable delivery. It supports signature verification for multiple sources like Stripe, GitHub, and Shopify, enabling agents to debug and fix webhook integration issues autonomously.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by AnyHook
MCP endpoint (Streamable HTTP)
https://anyhook.net/mcp
Vendor documentation

What you can do with it

  • Set up and configure webhook endpoints for AI agents
  • Monitor incoming webhook events and check delivery status
  • Replay failed webhook events to ensure successful processing
  • Verify webhook signatures from sources like Stripe and GitHub
Tools advertised by the last live check:
  • anyhook_mock
  • anyhook_verify
  • anyhook_providers
  • anyhook_apps_list
  • anyhook_inbox
  • anyhook_apps_create
  • anyhook_connect
  • anyhook_replay
  • anyhook_undelivered
  • anyhook_replay_failed
  • anyhook_events
  • anyhook_inspect

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http anyhook-mcp https://anyhook.net/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add anyhook-mcp --url https://anyhook.net/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable anyhook-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "anyhook-mcp": {
      "url": "https://anyhook.net/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "anyhook-mcp": {
      "type": "streamableHttp",
      "url": "https://anyhook.net/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start anyhook-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "anyhook-mcp": {
      "type": "http",
      "url": "https://anyhook.net/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http anyhook-mcp https://anyhook.net/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "anyhook-mcp": {
      "url": "https://anyhook.net/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "anyhook-mcp": {
      "serverUrl": "https://anyhook.net/mcp"
    }
  }
}

Do you run AnyHook MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing