What does this automation do?
An HTTP webhook receives the request, discovers the server tools, and calls the configured MCP tool with the incoming fields.
What can you do with it?
- Start an MCP tool call from another system
- Map webhook fields into a repeatable tool input
- Log the result on a Taskade task
The Steps
This automation runs in 4 steps:
- When HTTP — Webhook Received
- Then MCP Client — List Tools
- Then MCP Client — Call Tool
- Then Taskade — Add Task
Who is this automation for?
Built for teams exposing a controlled webhook entry point to an MCP-backed process. An HTTP webhook receives the request, discovers the server tools, and calls the configured MCP tool with the incoming fields.
How do you set it up?
- Open the "Automations" tab in your workspace.
- Click ➕ Add automation, then start from scratch.
- Add the trigger "Webhook Received" from HTTP.
- Add the action "List Tools" from MCP Client.
- Add the action "Call Tool" from MCP Client.
- Add the action "Add Task" from Taskade.
- Enable the toggle in the top-right corner to activate the automation.
Prefer to describe it instead? Click Build this flow with AI above and Taskade wires the trigger, the steps for you.