Kestra MCP server

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.

What you can automate

Real workflows

Check a flow’s status without opening the Kestra UI

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.

Frequently asked questions

Does this work with self-hosted Kestra?

Yes — it covers both self-hosted and cloud Kestra deployments.

What parts of a flow can it inspect?

Tasks, triggers, inputs, and outputs — the full definition of a YAML flow.

Start free

Plans

Free

$0/mo

Download without a card and start for free.

Individual

$50/mo

The full personal agent platform for one person.

Enterprise

$200/mo

Multiple workspaces and capacity for larger teams.

Related integrations

Explore: Skills · Glossary · Solutions · Use cases · Examples · Comparisons · Templates · Blog · Docs