🪝
Tag10 MCPs tagged here

Webhooks

MCPs that send, receive, or react to webhook events

TL;DR

Webhook MCP servers expose tools to register, receive, and process inbound HTTP events from SaaS platforms. They also send outbound webhooks to trigger downstream systems. Combined with automation MCPs, they form the event-driven core of any agentic workflow.

About Webhooks

Webhook MCPs are the glue between systems — they let agents receive HTTP callbacks from GitHub, Stripe, Shopify, Slack, and 100+ SaaS tools. Incoming webhooks trigger agent logic; outgoing webhooks send data elsewhere.

Common use cases

  • Trigger an agent the moment a Stripe payment succeeds
  • Auto-deploy on GitHub push webhook
  • Forward Linear issue events to a Slack channel with agent summaries
  • Turn Shopify order webhooks into inventory + tax + shipping workflows
  • Relay Discord messages into an internal agent for triage

Frequently asked questions

How do webhook MCPs receive events?

Most expose an ngrok-style tunnel or require you to point the SaaS webhook URL at a server endpoint. The MCP then parses the payload and surfaces it as a tool result.

Can I secure webhook MCPs?

Yes — always verify webhook signatures (e.g. Stripe's Stripe-Signature header). Most MCPs have built-in signature validation.

What's the difference between inbound and outbound?

Inbound = your MCP receives HTTP POSTs from a SaaS. Outbound = your MCP sends HTTP POSTs to trigger external systems. Most MCPs support both.

Can webhooks trigger long-running agent tasks?

Yes — pair webhook MCPs with task queue MCPs. The webhook enqueues a job, and the agent picks it up asynchronously.

Install Webhooks MCPs

Browse the full directory or explore all tags to find the right MCPs for your stack.