Bring Webhooks
to Cursor
Learn how to connect Make.com Webhook Trigger to Cursor and start using 1 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
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 Cursor?
Cursor's Agent mode turns Make.com Webhook Trigger into an in-editor superpower. Ask Cursor to generate code using live data from Make.com Webhook Trigger and it fetches, processes, and writes. all in a single agentic loop. 1 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Make.com Webhook Trigger in Cursor
Make.com Webhook Trigger and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Make.com Webhook Trigger to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
AEGIS Hedging
4 toolsEnergy risk management — manage trades, valuations, and market data via AI.
Arcadia Utility Cloud
6 toolsAutomate utility data collection with Arcadia Utility Cloud — track accounts, bills, and usage via AI.
Marketplacer (Enterprise Marketplace Platform)
9 toolsManage your enterprise marketplace via Marketplacer — list products, track orders, and audit seller networks.
UUID & ULID Generator
2 toolsStop LLMs from hallucinating fake or repeated IDs. Generate mathematically guaranteed v4 UUIDs and time-sortable ULIDs natively.