kestra-io/mcp-server-python

You can run the MCP Server in a Docker container. This is useful if you want to avoid managing Python environments or dependencies on your local machine.
Using Kestra AI Agent
See kestra_mcp_docker.
Minimal configuration for OSS users
Paste the following configuration into your MCP settings (e.g., Cursor, Claude, or VS Code):
Minimal configuration for EE users
Detailed Configuration using Docker
**Notes:**
- Replace , , and with your actual credentials.
- For OSS installations, you can use KESTRA_USERNAME and KESTRA_PASSWORD instead of KESTRA_API_TOKEN.
- To disable Enterprise Edition tools in OSS, set KESTRA_MCP_DISABLED_TOOLS=ee.
- The host.docker.internal hostname allows the Docker container to access services running on your host machine (such as the Kestra API server on port 8080). This works on macOS and Windows. On Linux, you may need to use the host network mode or set up a custom bridge.
- The -e flags pass environment variables from your MCP configuration into the Docker container.
---
Kestra version support
Both Kestra 1.x and Kestra 2.x are supported by the same image, and nothing has to be configured for either.
Several endpoints were changed in Kestra 2.0. The execution actions were moved under /actions/, the per-endpoint search parameters were replaced by the unified filters[field][OPERATION] model, backfill creation was moved to /triggers/backfill/create, and KV listing was moved to GET /kv. A 1.x query parameter sent to a 2.x server is ignored rather than rejected, so a request can appear to succeed while the results come back unfiltered.
The server version is read once from GET /api/v1/configs on the first tool call and every request is then built for that major. Where that endpoint is unreachable, behind a proxy that does not forward it for instance, the major can be set explicitly:
Two differences between the majors remain visible in the tool output:
- **Dashboards** - from 2.0 on, dashboards can only be created over the API in the Enterprise Edition, so generate_dashboard with auto_create returns the generated YAML together with a warning on OSS 2.x.
- **Namespace file moves** - on Kestra 2.x, a file written to a path that was previously moved away is stored under a versioned name, and a later move of that path fails with a 500. The error is reported with the suggestion to delete and re-upload instead.
---
Available Tools
- 🔄 backfill
- ⚙️ ee (Enterprise Edition tools)
- ▶️ execution
- 📁 files
- 🔀 flow
- 🗝️ kv
- 📋 logs
- 🌐 namespace
- 🔁 replay
- ♻️ restart
- ⏸️ resume
**Note:** The ee tool group contains Enterprise Edition specific functionality and is only available in EE/Cloud editions. For OSS users, you can disable EE tools by adding KESTRA_MCP_DISABLED_TOOLS=ee to your .env file.
Optionally, you can include KESTRA_MCP_DISABLED_TOOLS in your .env file listing the tools that you prefer to disable. For example, if you want to disable Namespace Files tools, add this to your .env file:
To disable multiple tools, separate them with comma:
Logging Configuration
By default, the MCP server only logs ERROR level messages to minimize noise. You can control the logging level using the KESTRA_MCP_LOG_LEVEL environment variable: