Reliable infrastructure for webhooks and external events. Event Gateway: https://xitter.cf/t.co/G5BseCXH3s Outpost: https://xitter.cf/t.co/HQRZC8H4zR
Joined December 2020
- Tweets1.1K
- Following72
- Followers1.4K
- Likes1.1K
Check out the full write-up and repos: hookdeck.com/blog/binary-pay…
It works the other way too. Return a Buffer, set content-type, and the destination gets a file.
Our demo turns JSON events into a PNG receipt, a WAV chime, a PDF invoice and an SVG chart. Uses Node built-ins, not npm packages.
Transformations now run on a Node.js-compatible runtime:
- node:zlib, node:crypto, node:buffer
- ES modules and async handlers
- npm packages bundled with esbuild
Gzip-compressed JSON in, JSON you can filter and search out:
Point a @DeepgramAI text-to-speech callback at a Hookdeck source and the MP3 reaches your server with its original bytes, Content-Type and Content-Length.
Same on retries and replays.
Not every webhook is JSON.
Hookdeck Event Gateway now delivers audio, images, PDFs, archives, protobuf and multipart uploads byte for byte.
Transformations run Node.js too, so you can gunzip a batch, parse a PDF, or turn a JSON event into a PNG.
@leggetter shows us how 🧵
The full 6-minute explainer, and more on MCP Events ↓
hkdk.link/mcp-events
To try it now, we built the MCP Events bridge: an open-source MCP server that turns webhooks from GitHub, Resend or any service that sends them into MCP events. It runs on Hookdeck Event Gateway.
github.com/hookdeck/mcp-even…
Who supports it so far: ChatGPT on the client side, webhook mode only. Inline, Vercel's mcp-handler and Alpic's Skybridge on the server side. No official MCP SDK support yet.
Webhook mode is the one with traction. The client subscribes with a callback URL and its own secret, the server verifies the endpoint with a signed challenge, and each event then arrives signed using Standard Webhooks.
Three delivery modes: poll works almost anywhere but adds latency, push is a stream the client holds open, and webhook has the server POST each event to the client's URL. The client's SDK picks a mode the event type supports.
The client calls events/list and subscribes to an event type with arguments, such as which repo to watch. Every event has the same fields: an ID, the type, a timestamp and the data. A cursor lets the client resume, if the event type supports replay.
MCP Events is the hop from the MCP server to the MCP client in your agent's host, like ChatGPT. How the server hears about the event (here, a GitHub webhook) is outside the spec.
MCP is request-driven. To catch a failed build, the client polls, or a script outside MCP prompts the agent. Notifications don't fill the gap: no payload, and one sent while the client is disconnected is lost.
Hookdeck retweeted
Made a 6-minute explainer on MCP Events, the draft MCP extension (SEP-3415) that lets your agent subscribe to events instead of waiting for a prompt.
Hookdeck retweeted
This is it! The Shopify community lunch in London has landed!
@TSupportHeroes @Hookdeck @capitaliply and @DiscountKit have made it possible to get a lovely bunch of @Shopify folk together enjoying great talks and delicious food in the heart or London City 🏰
🚨DISPATCH FROM FARRINGDON:
The hour has arrived.
Today, the annual gathering of the Shopify ecosystem converges upon Origin City. Founders, agency minds, investors, and an assortment of exceptionally good people gathered under one roof for exceptional food and unscripted conversation.
🍽 Time: 11:45 AM – 2:00 PM
📍 Venue: Origin City Restaurant, Farringdon
A massive thank you to our incredible sponsors for making this edition possible:
@TSupportHeroes | @Hookdeck | @DiscountKit | @capitaliply
