How to Use the Make.com Webhook Trigger MCP in Google ADK

Q: How do I initialize the Make.com Webhook Trigger MCP Server inside Google ADK?

Install the library using pip install google-adk and import the toolset components. You instantiate McpToolset using StreamableHttpServerParameters pointing to your Vinkius endpoint, then pass that toolset directly into your LlmAgent constructor's tools list.

Q: Can I restrict which Google ADK agents can access the Make.com Webhook Trigger?

Yes, you can use the toolnames filter within the McpToolset configuration to expose only triggermakewebhook to specific agents. This prevents unauthorized Gemini agents in your Google ADK environment from triggering external workflows.

Q: How does the Make.com Webhook Trigger handle large payloads from Google ADK?

The triggermakewebhook tool accepts standard JSON strings. While Gemini can process huge context windows, Make.com webhooks have payload size limits. You should instruct your Google ADK agent to summarize or structure the JSON payload to stay within Make's limits.

Connect Gemini's long-context reasoning in Google ADK to thousands of apps via the Make.com Webhook Trigger MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Make.com Webhook Trigger MCP to Google ADK

Create your Vinkius account to connect Make.com Webhook Trigger to Google ADK and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Make.com Webhook Trigger with Google ADK

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Connect BigQuery data to Make via Google ADK

Google's enterprise framework thrives on processing massive datasets. When your agent extracts insights from BigQuery or Vertex AI, it can immediately push those results to external systems using the `trigger_make_webhook` tool. This bridges your Google Cloud data directly with your visual workflows. Instead of writing custom Google Cloud Functions to handle outbound API calls, you let the MCP server handle the connection. Your Gemini models use their 1M+ token context to summarize data, then format the perfect JSON payload to trigger your Make scenarios.

Granular tool control for enterprise security

Enterprise deployments require strict access controls. Google ADK lets you use the `tool_names` filter on your `McpToolset` to selectively expose only the `trigger_make_webhook` tool from the MCP server. This setup ensures your Gemini agent only interacts with authorized webhook endpoints. You maintain a clean security boundary between your internal Google Cloud resources and external automation platforms.

Direct HTTP transport integration

You can configure the connection to the `trigger_make_webhook` tool using the SDK's `StreamableHttpServerParameters`. Passing the initialized `McpToolset` to your `LlmAgent` takes a single line of code. From that point on, the model can autonomously decide when a workflow requires external execution via Make.com.

Setup guide

Set up Make.com Webhook Trigger MCP in Google ADK

Prerequisites

Python 3.10+ installed
google-adk package (pip install google-adk)
Active Vinkius subscription with a valid endpoint token

1

Install Google ADK

Run pip install google-adk to install the Agent Development Kit. MCP support is included via the McpToolset class.
2

Connect via SSE transport

Use McpToolset.from_server() with SseServerParams pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Create an LlmAgent

Pass the returned mcp_tools list directly to LlmAgent(tools=mcp_tools). The ADK maps each MCP tool to a native Gemini function call — no manual schema definitions required.
4

Run with any Gemini model

The agent works with any Gemini model (gemini-2.0-flash, gemini-2.5-pro, etc.). Copy the full example on the right to get started with Make.com Webhook Trigger tools in your ADK agent.

agent.py

from google.adk.agents import LlmAgent
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import SseServerParams

# Connect to the MCP via SSE
mcp_tools, exit_stack = await McpToolset.from_server(
    connection_params=SseServerParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    )
)

# Create your agent with auto-discovered tools
agent = LlmAgent(
    name="Make.com Webhook Trigger_agent",
    model="gemini-2.0-flash",
    instruction="You have access to Make.com Webhook Trigger tools via MCP.",
    tools=mcp_tools,
)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Make (Integromat). All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Make.com Webhook Trigger now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Make.com Webhook Trigger MCP in Google ADK

Install the library using `pip install google-adk` and import the toolset components. You instantiate `McpToolset` using `StreamableHttpServerParameters` pointing to your Vinkius endpoint, then pass that toolset directly into your `LlmAgent` constructor's tools list.

Yes, you can use the `tool_names` filter within the `McpToolset` configuration to expose only `trigger_make_webhook` to specific agents. This prevents unauthorized Gemini agents in your Google ADK environment from triggering external workflows.

The `trigger_make_webhook` tool accepts standard JSON strings. While Gemini can process huge context windows, Make.com webhooks have payload size limits. You should instruct your Google ADK agent to summarize or structure the JSON payload to stay within Make's limits.

No. Vinkius hosts the MCP server in a secure sandbox. Your Google ADK client connects to it remotely over HTTP, so you don't have to manage any local runtime infrastructure or background processes.

Yes. All transmissions of your webhook URLs and JSON payload strings are encrypted in transit via HTTPS. The Vinkius runtime executes the request in an isolated, ephemeral V8 sandbox that destroys all session data immediately after the webhook is triggered.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript