Kestra workflows are defined as YAML flows with their own tasks, triggers, inputs, and outputs, and keeping tabs on them across self-hosted or cloud deployments usually means jumping into the Kestra UI. Connected to Neotask, the Kestra MCP server lets you inspect and manage those flows directly — asking about a trigger, an output, or a task's status without leaving the conversation.
Ask Neotask about a specific flow's triggers or recent outputs. It inspects the flow directly through Kestra and reports back what's configured and what ran.
Yes — it covers both self-hosted and cloud Kestra deployments.
Tasks, triggers, inputs, and outputs — the full definition of a YAML flow.
$0/mo
Download without a card and start for free.
$50/mo
The full personal agent platform for one person.
$100/mo
One company workspace with room to add your team.
$200/mo
Multiple workspaces and capacity for larger teams.
Explore: Skills · Glossary · Solutions · Use cases · Examples · Comparisons · Templates · Blog · Docs