Webhook MCP Server

MCP server para fazer requisições HTTP para webhooks com parâmetros dinâmicos

Local serverstdioTypeScript

What is the Webhook MCP MCP server?

MCP server para fazer requisições HTTP para webhooks com parâmetros dinâmicos. Exposed over MCP by the webhook mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Um servidor MCP (Model Context Protocol) para enviar requisições HTTP para webhooks com parâmetros dinâmicos.

Its toolset

Everything the assistant can do here goes through one of these:

  • macOS — ~/Library/Application Support/Claude/claude_desktop_config.json
  • Authorization — deve ser no formato Bearer
  • Content-Type — deve ser application/json, application/x-www-form-urlencoded ou application/xml
  • send_webhook — Envia uma requisição HTTP para um webhook com parâmetros personalizados

Configuration

You will need 5 environment variables: WHITELIST_URLS, LOG_LEVEL, RETRY_ATTEMPTS, RETRY_BASE_DELAY_MS, LANG. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at ts-node on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Webhook MCP's toolset — macOS, Authorization, Content-Type and 1 more — is a fair guide to whether it matches your workflow. It is maintained by rafabarbosa; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Webhook MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the webhook mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
macOS~/Library/Application Support/Claude/claude_desktop_config.json
Authorizationdeve ser no formato Bearer <token>
Content-Typedeve ser application/json, application/x-www-form-urlencoded ou application/xml
send_webhookEnvia uma requisição HTTP para um webhook com parâmetros personalizados.

How to install the Webhook MCP MCP server

{
  "mcpServers": {
    "webhooks": {
      "command": "node",
      "args": ["/Users/rafabarbosa/Desktop/scripts/webhooks-mcp/dist/index.js"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
WHITELIST_URLSEndpoint or connection string the server talks to.Yes
LOG_LEVELConfiguration value read at startup.Optional
RETRY_ATTEMPTSConfiguration value read at startup.Optional
RETRY_BASE_DELAY_MSConfiguration value read at startup.Optional
LANGConfiguration value read at startup.Optional

Example prompts to try

  • Use Webhook MCP to macOS.
  • Use Webhook MCP to Authorization.
  • Use Webhook MCP to Content-Type.

Frequently asked questions

It connects Webhook MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (macOS, Authorization, Content-Type, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Webhook MCP directly.