ZenML MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOGLEVEL | No | Log level for the server | INFO |
| NO_COLOR | No | Disable colored output | 1 |
| ZENML_STORE_URL | Yes | The URL of your ZenML server (e.g., https://d534d987a-zenml.cloudinfra.zenml.io) | |
| PYTHONIOENCODING | No | Python IO encoding | UTF-8 |
| PYTHONUNBUFFERED | No | Python unbuffered mode | 1 |
| ZENML_STORE_API_KEY | Yes | The API key for your ZenML server |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| diagnose_zenml_setupA | Diagnose ZenML MCP server setup (env vars, connectivity, auth, versions). Returns structured diagnostics about the server's configuration and connectivity. This tool works even when the ZenML SDK is not installed or environment variables are missing - use it to troubleshoot setup issues. |
| get_step_logsA | Get the logs for a specific step run. |
| zenml_describe_resourcesA | Discover supported generic ZenML resources or one operation schema. With no arguments this returns a short catalog. Pass a canonical singular resource type to inspect its operations, and add an operation name for its bounded input schema and a small example. |
| zenml_list_resourcesA | List one allowlisted ZenML resource type with validated filters. |
| zenml_get_resourceB | Get one allowlisted ZenML resource by its identifier. Artifact versions, model versions, and run steps require their parent identifier. Stack components require their fixed component type. |
| zenml_create_resourceA | Create one allowlisted ZenML resource with a strict typed payload. |
| zenml_update_resourceB | Update one exact UUID through an allowlisted operation-specific payload. |
| zenml_delete_resourceB | Delete or archive one exact UUID using bounded destructive options. |
| zenml_action_resourceA | Run one finite ZenML lifecycle or relation action. |
| get_active_userA | Get the currently active user. |
| get_active_projectB | Get the currently active project. Projects are organizational containers for ZenML resources. Most SDK methods are project-scoped, and this tool returns the default project context. |
| trigger_pipelineA | Trigger a pipeline to run from the server. |
| get_deployment_logsB | Get logs for a specific deployment. |
| get_step_codeC | Get the code for a step. |
| open_pipeline_run_dashboardA | Open an interactive dashboard of recent ZenML pipeline runs. The dashboard shows pipeline runs with status indicators, expandable step details, filtering, and drill-down into step logs — all in an interactive UI. The dashboard fetches its own data dynamically. |
| open_run_activity_chartA | Open an interactive chart showing pipeline run activity over the last 30 days. Shows a bar chart with daily run counts, hover tooltips, and status breakdown (completed in green, failed in red, other in amber). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| stack_components_analysis | Analyze the stacks in the ZenML workspace. |
| recent_runs_analysis | Analyze the recent runs in the ZenML workspace. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| zenml_resource_catalog | Return the bounded generic-resource catalog without detailed schemas. |
| pipeline_runs_dashboard_ui | ZenML MCP App: Pipeline Run Dashboard (HTML entrypoint). |
| run_activity_chart_ui | ZenML MCP App: Run Activity Chart (HTML entrypoint). |
| list_apps | List available MCP Apps provided by this server. |
TDQS
Scored across 16 tools
Each tool has a distinct purpose: resource CRUD operations are clearly separated by verb (list, get, create, update, delete, action), and specific tools for logs, code, diagnostics, and dashboards are differentiated by target entity (step, deployment, pipeline, user, project). No two tools appear to perform the same function.
The tool names follow a predictable pattern: generic resource operations all use the 'zenml_<verb>_resource' convention, while specific operations use descriptive verbs like 'get_', 'open_', 'trigger_', and 'diagnose_'. This creates two consistent sub-patterns, but the mix is still readable and distinguishable.
With 16 tools, the server is slightly above the typical 3-15 range but still well-scoped for a comprehensive ZenML MCP server. Each tool serves a clear purpose, covering resource management, pipeline execution, logging, diagnostics, and visualization without redundancy.
The tool set provides full CRUD and lifecycle coverage through the generic resource tools, supplemented by specific operations for pipeline triggering, log retrieval, step code, and user/project context. The dashboard and chart tools offer monitoring capabilities, leaving no obvious gaps for common ZenML workflows.