send_webhookLABSCO SUMMARY
Set the allowlist before you connect it.
This is a generic outbound HTTP tool, which makes it useful for wiring an agent into anything with a webhook — CRM intake, Slack notifications, payment callbacks — and also means an unconstrained instance will post wherever the model composes a URL. WHITELIST_URLS is the control: with it unset, any URL is permitted, so list your domains first and treat that as part of the install rather than a hardening step for later.
What it is
A TypeScript MCP server that sends HTTP requests to webhooks with dynamic parameters, validated on the way out and logged on the way back.
What you get
send_webhook— aurl, amethodfrom GET, POST, PUT, PATCH and DELETE, plus optionalparameters,headersandtimeout- Method-aware parameter placement: GET and DELETE put them in the query string, POST, PUT and PATCH send them as a JSON body
- Input validation with Zod, and header checks — Authorization must be a bearer token, Content-Type must be JSON, form-encoded or XML
- A domain allowlist through
WHITELIST_URLS, so the destinations are yours to decide - Automatic retries with exponential backoff via
RETRY_ATTEMPTSandRETRY_BASE_DELAY_MS - Configurable log verbosity with
LOG_LEVEL, and messages in Portuguese or English throughLANG
Requirements
npm install and npm run build, then point the client at the built dist/index.js. A Docker path exists too, taking the same environment variables. The request timeout defaults to 30000 milliseconds and the retry count to 1.
Setup effort
Build from source — git clone https://github.com/rafabarbosa/webhook_mcp
USE CASES
Dropping a record into another system
Send a POST with the fields as parameters; the server places them in the JSON body for you.
Constraining where an agent can post
Set the allowlist to your own domains and restart, so calls to anything else are refused with a clear message.
Surviving a flaky endpoint
Raise the retry count and base delay so transient failures back off and retry instead of failing the turn.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
git clone https://github.com/rafabarbosa/webhook_mcp
cd webhook_mcp
npm install
npm run buildMCP Clients
Claude Desktop
{
"mcpServers": {
"webhooks": {
"command": "node",
"args": [
"<YOUR_PATH_TO_WEBHOOK_MCP>/dist/index.js"
]
}
}
}