MCP server for inspecting, analyzing, and triggering ZenML MLOps and LLMOps pipeline resources.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by MCP Zenml.
get_snapshotGet a frozen pipeline configuration by name/ID
list_snapshotsList snapshots with filters (runnable, deployable, deployed, tag)
get_deploymentGet a deployment's runtime status and URL
list_deploymentsList deployments with filters (status, pipeline, tag)
get_deployment_logsGet bounded logs from a deployment (tail=100 default, max 1000)
trigger_pipelineTrigger a pipeline run (prefer `snapshot_name_or_id` parameter)
This project implements a Model Context Protocol (MCP) server for interacting with the ZenML API.

The Model Context Protocol (MCP) is an open protocol that standardizes how applications provide context to Large Language Models (LLMs). It acts like a "USB-C port for AI applications" - providing a standardized way to connect AI models to different data sources and tools.
MCP follows a client-server architecture where:
ZenML is an open-source platform for building and managing ML and AI pipelines. It provides a unified interface for managing data, models, and experiments.
For more information, see the ZenML website and our documentation.
The server provides MCP tools to access core read functionality from the ZenML server, providing a way to get live information about:
The server also allows you to trigger new pipeline runs using snapshots (preferred) or run templates (deprecated).
Note: We're continuously improving this integration based on user feedback. Please join our Slack community to share your experience and help us make it even better!
The MCP server exposes the following tools, grouped by category:
| Tool | Description |
|---|---|
get_snapshot | Get a frozen pipeline configuration by name/ID |
list_snapshots | List snapshots with filters (runnable, deployable, deployed, tag) |
get_deployment | Get a deployment's runtime status and URL |
list_deployments | List deployments with filters (status, pipeline, tag) |
get_deployment_logs | Get bounded logs from a deployment (tail=100 default, max 1000) |
trigger_pipeline | Trigger a pipeline run (prefer snapshot_name_or_id parameter) |
| Tool | Description |
|---|---|
get_active_project | Get the currently active project |
get_project | Get project details by name/ID |
list_projects | List all projects |
get_tag | Get tag details (exclusive, colors) |
list_tags | List tags with filters (resource_type) |
get_build | Get build details (image, code embedding) |
list_builds | List builds with filters (is_local, contains_code) |
| Tool | Description |
|---|---|
get_user, list_users, get_active_user | User management |
get_stack, list_stacks | Stack configurations |
get_stack_component, list_stack_components | Stack components |
get_flavor, list_flavors | Component flavors |
get_service_connector, list_service_connectors | Cloud connectors |
get_pipeline_run, list_pipeline_runs | Pipeline runs |
get_run_step, list_run_steps | Step details |
get_step_logs, get_step_code | Step logs and source code |
list_pipelines, get_pipeline_details | Pipeline definitions |
get_schedule, list_schedules | Schedules |
list_artifacts | Artifact metadata |
list_secrets | Secret names (not values) |
get_service, list_services | Model services |
get_model, list_models | Model registry |
get_model_version, list_model_versions | Model versions |
| Tool | Description |
|---|---|
open_pipeline_run_dashboard | Open interactive pipeline runs dashboard (MCP App) |
open_run_activity_chart | Open 30-day run activity bar chart (MCP App) |
| Tool | Description |
|---|---|
stack_components_analysis | Analyze stack component usage |
recent_runs_analysis | Analyze recent pipeline runs |
most_recent_runs | Get N most recent runs |
| Tool | Description |
|---|---|
diagnose_zenml_setup | Diagnose server setup (env vars, SDK, connectivity, auth). Works even when misconfigured. |
| Tool | Replacement |
|---|---|
get_run_template | Use get_snapshot instead |
list_run_templates | Use list_snapshots instead |
trigger_pipeline(template_id=...) | Use trigger_pipeline(snapshot_name_or_id=...) |
Why the change? ZenML evolved its "runnable pipeline artifact" concept. Run Templates are now deprecated wrappers that internally just point to Snapshots. New code should use Snapshots directly.
| Old Pattern (Templates) | New Pattern (Snapshots) |
|---|---|
list_run_templates() | list_snapshots(runnable=True, named_only=True) |
get_run_template(name) | get_snapshot(name, include_config_schema=True) |
trigger_pipeline(template_id=...) | trigger_pipeline(snapshot_name_or_id=...) |
Note: get_deployment_logs returns bounded output (default 100 lines, max 1000, capped at 100KB) and requires the appropriate deployer integration to be installed.
The easiest way to set up the ZenML MCP Server is through your ZenML dashboard's MCP Settings page.

Navigate to Settings → MCP in your ZenML dashboard to get:
The MCP Settings page lets you generate a Personal Access Token (PAT) with a single click. The token is automatically included in all generated configuration snippets.
Prefer manual setup? See the detailed instructions below.
What are MCP Apps? MCP Apps are interactive HTML UIs that MCP servers can serve directly into AI clients. They render in sandboxed iframes and can call server tools bidirectionally. See the official announcement for full details.

This server includes two experimental MCP Apps:
| App | Tool | Description |
|---|---|---|
| Pipeline Runs Dashboard | open_pipeline_run_dashboard | Interactive table of recent pipeline runs with status, step details, and logs |
| Run Activity Chart | open_run_activity_chart | Bar chart of pipeline run activity over the last 30 days with status breakdown |

These apps are included as proof-of-concept examples. We welcome feedback and contributions for more MCP Apps. It is still early days for this new feature so we'll have to see how it evolves. We expect to support it more fully in the future.
MCP Apps require Streamable HTTP transport (not stdio). The following clients currently support MCP Apps:
Factual signals from GitHub, npm, and our automated checks — not a rating.
No reviews yet — be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/zenml-io-mcp-zenml)<a href="https://allmcps.com/mcp/zenml-io-mcp-zenml"><img src="https://allmcps.com/api/badge/zenml-io-mcp-zenml?style=directory" alt="MCP Zenml on AllMCPs" /></a>