---
title: "Kestra MCP Server: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/kestra/
description: "Inspect and operate Kestra workflows, executions, namespace files and KV data through the publisher Python adapter."
---

# Kestra MCP Server: review, setup & limitations · Undominated.ai

> Inspect and operate Kestra workflows, executions, namespace files and KV data through the publisher Python adapter.

[← Explore all mcp servers](/mcp-servers/)

WORKFLOW ORCHESTRATION / Kestra

# Kestra MCP Server

Inspect and operate Kestra workflows, executions, namespace files and KV data through the publisher Python adapter.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/kestra-io/mcp-server-python)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 4 linked sources
 Publisher Kestra
 Licence [Apache-2.0 ↗](https://github.com/kestra-io/mcp-server-python/blob/a15806feeb8a8828e92ac4f23739fa4a14a37414/LICENSE)
 Revision a15806feeb8a
 [Read what was—and wasn’t—checked ↓](#review)

“Kestra Python MCP Server”

 [Kestra · upstream description ↗](https://github.com/kestra-io/mcp-server-python/blob/a15806feeb8a8828e92ac4f23739fa4a14a37414/README.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Documents OSS versus Enterprise authentication and tool-group selection.
- Handles differences in Kestra 1.x and 2.x request formats explicitly.
- The pinned README runs a Kestra MCP server in Docker against a Kestra API, with separate OSS and Enterprise credential examples.
- Enterprise-only tools can be disabled, and dashboard creation on OSS 2.x does not silently succeed.

### A good fit for

 - Read a failed execution and its logs before preparing a flow correction.
- Review namespace files and execution state before deliberately replaying a workflow.
- Driving a local Kestra OSS API from Cursor, Claude, or VS Code
- An Enterprise Kestra instance where the client should use an API token

### Weigh up before choosing

 - Execution, flow, file and KV groups can mutate state; disabling ee only removes Enterprise tools, not writes.
- If /api/v1/configs is blocked by a proxy, set KESTRA_API_VERSION explicitly; older search parameters can otherwise appear successful while not filtering.
- Docker host.docker.internal needs additional networking configuration on some Linux hosts.
- OSS users are told to set KESTRA_MCP_DISABLED_TOOLS=ee.
- generate_dashboard with auto_create on OSS 2.x returns YAML and a warning instead of creating the dashboard.
- host.docker.internal is not the same on Linux.
- A pin does not verify transitive dependencies.
- This review did not execute the resource.
- Disabling one group does not restrict the bearer token itself; verify tenant routing separately from authentication and group registration.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - README.md
- LICENSE at the pinned revision
- src/server.py
- requirements.txt
- LICENSE
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

### Our findings

 - src/server.py gives BasicAuth precedence when both username/password are present, otherwise uses the bearer token.
- Disabled groups are omitted at registration; the entrypoint explicitly starts stdio.
- The Docker image talks to a Kestra API. OSS examples use a username and password; Enterprise examples use KESTRA_API_TOKEN.
- The ee tool group is Enterprise-only. On OSS, KESTRA_MCP_DISABLED_TOOLS=ee turns those tools off, and generate_dashboard cannot create a dashboard through the API on OSS 2.x.
- With stdio, the IDE launches the process. The README does not claim the container can reach the host on Linux without host networking or a bridge.
- The client applies the configured tenant to its API path and X-Kestra-Tenant header, so tenant configuration affects the destination of every operation.

### Not established by this review

 - Server startup, authentication, live tool execution and security isolation were not tested.
- Published package/container parity with a source revision and hosted implementation internals were not tested.
- The server was not started and its tools were not called.
- A pin does not verify transitive dependencies.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://github.com/kestra-io/mcp-server-python/blob/a15806feeb8a8828e92ac4f23739fa4a14a37414/README.md)

DOCUMENTED COMMAND

 docker run -i --rm -e KESTRA_BASE_URL -e KESTRA_TENANT_ID -e KESTRA_API_TOKEN -e KESTRA_MCP_DISABLED_TOOLS ghcr.io/kestra-io/mcp-server-python:latest Copy command ↗

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

 - Set KESTRA_BASE_URL to the reachable API /api/v1 path and KESTRA_TENANT_ID if needed.
- For EE/Cloud supply KESTRA_API_TOKEN. For OSS use the documented KESTRA_USERNAME/KESTRA_PASSWORD Docker environment flags and disable ee.
- Disable unneeded groups with KESTRA_MCP_DISABLED_TOOLS; inspect execution and flow permissions on the Kestra identity before enabling changes.
- Set KESTRA_TENANT_ID for the intended EE/Cloud tenant and list disabled tool groups explicitly as comma-separated names before launching stdio.

### Before you start

 - Docker and a stdio MCP client, plus a reachable Kestra API.
- Edition-appropriate credentials; source development instead requires Python 3.13 and requirements.txt.

### Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

 {
 "mcpServers": {
 "kestra": {
 "command": "docker",
 "args": [
 "run",
 "-i",
 "--rm",
 "-e",
 "KESTRA_BASE_URL",
 "-e",
 "KESTRA_TENANT_ID",
 "-e",
 "KESTRA_API_TOKEN",
 "-e",
 "KESTRA_MCP_DISABLED_TOOLS",
 "ghcr.io/kestra-io/mcp-server-python:latest"
 ]
 }
 }
} Copy configuration ↗

### Compatibility

Docker and a stdio MCP client, plus a reachable Kestra API. · Edition-appropriate credentials; source development instead requires Python 3.13 and requirements.txt.

### Implementation

Python

### Transports

stdio

### Workflow orchestration

 - Uses the supplied Kestra identity for API operations, including execution actions and file/KV changes.
- Group filtering affects tool registration; it does not narrow the underlying account permissions.

### Cost model

Kestra hosting, workflow executions and any downstream services incur their normal costs.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Publisher setup, capabilities and operating boundaries ↗](https://github.com/kestra-io/mcp-server-python/blob/a15806feeb8a8828e92ac4f23739fa4a14a37414/README.md) Checked 2026-10-14 https://github.com/kestra-io/mcp-server-python/blob/a15806feeb8a8828e92ac4f23739fa4a14a37414/README.md Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports
- [Pinned implementation: src/server.py ↗](https://github.com/kestra-io/mcp-server-python/blob/a15806feeb8a8828e92ac4f23739fa4a14a37414/src/server.py) Checked 2026-10-14 https://github.com/kestra-io/mcp-server-python/blob/a15806feeb8a8828e92ac4f23739fa4a14a37414/src/server.py Supports: review, install, access, limitations
- [Pinned implementation: requirements.txt ↗](https://github.com/kestra-io/mcp-server-python/blob/a15806feeb8a8828e92ac4f23739fa4a14a37414/requirements.txt) Checked 2026-10-14 https://github.com/kestra-io/mcp-server-python/blob/a15806feeb8a8828e92ac4f23739fa4a14a37414/requirements.txt Supports: review, install, access, limitations
- [Applicable licence text ↗](https://github.com/kestra-io/mcp-server-python/blob/a15806feeb8a8828e92ac4f23739fa4a14a37414/LICENSE) Checked 2026-10-14 https://github.com/kestra-io/mcp-server-python/blob/a15806feeb8a8828e92ac4f23739fa4a14a37414/LICENSE Supports: license

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
