MCPs that send, receive, or react to webhook events
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.
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.
Every push to main triggers a Supabase migration automatically. Schema diffs are committed and applied with zero manual steps.
Receive a Slack message for every successful payment, failed charge, and subscription cancellation in real time.
Sentry new issues are de-duplicated, enriched with commit info, and routed to the right Slack channel based on project.
Scrape Product Hunt daily with Firecrawl and send trending posts in your category to Slack so your team never misses a launch.
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.
Yes — always verify webhook signatures (e.g. Stripe's Stripe-Signature header). Most MCPs have built-in signature validation.
Inbound = your MCP receives HTTP POSTs from a SaaS. Outbound = your MCP sends HTTP POSTs to trigger external systems. Most MCPs support both.
Yes — pair webhook MCPs with task queue MCPs. The webhook enqueues a job, and the agent picks it up asynchronously.
Browse the full marketplace or explore all tags to find the right MCPs for your stack.