Compatible with every major AI agent and IDE
What is the Make.com Webhook Trigger MCP Server?
We refused to build thousands of individual MCP integrations for every SaaS app in the world. Instead, this MCP server provides a universal, zero-trust bridge to Make.com (formerly Integromat): just triggering a Custom Webhook.
Your AI agent gains the immediate, zero-friction ability to kick off complex workflows—like generating contracts, issuing invoices, or adding contacts to CRMs—by simply dumping a structured JSON payload into a Make.com scenario.
The Superpowers
- The Ultimate Joker Card: Why code a custom API integration when you can just build a scenario in Make? The agent sends the data, and Make does the visual routing to over 5,000+ apps.
- Zero-Bloat Integration: No massive SDKs. It uses a direct
POSTfetch to your specific Make Custom Webhook URL. You just provide the URL and the AI provides the JSON. - Absolute Containment: Because this is strictly a sending tool (Push only), the agent cannot read your Make.com account, cannot edit your scenarios, and cannot access other webhooks. It is a secure, one-way trigger.
Built-in capabilities (1)
com scenario. Provide the data you want to send in the "payloadJson" parameter as a valid JSON string. The Make scenario will receive this data and process it. Send a JSON payload to a Make.com (Integromat) Custom Webhook to trigger an automation scenario
Why Vercel AI SDK?
The Vercel AI SDK gives every Make.com Webhook Trigger tool full TypeScript type inference, IDE autocomplete, and compile-time error checking. Connect 1 tools through Vinkius and stream results progressively to React, Svelte, or Vue components. works on Edge Functions, Cloudflare Workers, and any Node.js runtime.
- —
TypeScript-first: every MCP tool gets full type inference, IDE autocomplete, and compile-time error checking out of the box
- —
Framework-agnostic core works with Next.js, Nuxt, SvelteKit, or any Node.js runtime. same Make.com Webhook Trigger integration everywhere
- —
Built-in streaming UI primitives let you display Make.com Webhook Trigger tool results progressively in React, Svelte, or Vue components
- —
Edge-compatible: the AI SDK runs on Vercel Edge Functions, Cloudflare Workers, and other edge runtimes for minimal latency
Make.com Webhook Trigger in Vercel AI SDK
Make.com Webhook Trigger and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Make.com Webhook Trigger to Vercel AI SDK through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Make.com Webhook Trigger in Vercel AI SDK
The Make.com Webhook Trigger MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 1 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Vercel AI SDK only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Make.com Webhook Trigger for Vercel AI SDK
Every tool call from Vercel AI SDK to the Make.com Webhook Trigger MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can the agent receive responses back from Make.com with this?
No. Make Webhooks respond immediately with 'Accepted'. The agent cannot wait for the scenario to finish executing or retrieve data from the final step of the Make scenario. This is strictly a 'fire and forget' trigger.
Do I need a paid Make.com account?
No. You can use Custom Webhooks on the free tier of Make.com. You just need to create a new scenario starting with the 'Custom Webhook' module.
How does the Vercel AI SDK connect to MCP servers?
Import createMCPClient from @ai-sdk/mcp and pass the server URL. The SDK discovers all tools and provides typed TypeScript interfaces for each one.
Can I use MCP tools in Edge Functions?
Yes. The AI SDK is fully edge-compatible. MCP connections work on Vercel Edge Functions, Cloudflare Workers, and similar runtimes.
Does it support streaming tool results?
Yes. The SDK provides streaming primitives like useChat and streamText that handle tool calls and display results progressively in the UI.
createMCPClient is not a function
Install: npm install @ai-sdk/mcp
Explore More MCP Servers
View all →
Atlassian Crowd
10 toolsEquip your AI agent to manage users, groups, and directory memberships via the Atlassian Crowd API.

Riot Games
12 toolsAccess League of Legends player data — summoner profiles, match history, ranked stats, champion masteries and live games.

TheCocktailDB Alternative
12 toolsGlobal cocktail database — search recipes, ingredients, and mixology guides via AI.

Missive
10 toolsCollaborative email and shared inbox for teams.
