This MCP server exposes ZenML API functionality through the Model Context Protocol, allowing clients to read ZenML entities such as projects, pipelines, runs, deployments, models, and related metadata. It also supports triggering pipeline runs from snapshots and includes diagnostics plus two experimental interactive MCP apps.
From the registry: MCP server for ZenML - browse stacks, pipelines, runs, artifacts & trigger pipeline runs via API

Please install the `mcp-zenml` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **ZenML server** — Deployed ZenML server >= 0.93.0 (https://cloud.zenml.io)
- **ZenML service account token** — Create a service account and generate an API key in the ZenML UI
Canonical MCP server config (stdio transport):
- command: `docker`
- args: ["run","-i","--rm","-e","ZENML_STORE_URL","-e","ZENML_STORE_API_KEY","zenmldocker/mcp-zenml:latest"]
- required environment variables:
- `ZENML_STORE_URL`: ZenML server URL (example: `https://your-zenml-server.example.com`)
- `ZENML_STORE_API_KEY`: ZenML service account API key (example: `<your-api-key>`)
- optional environment variables:
- `ZENML_ACTIVE_PROJECT_ID`: Active ZenML project ID (required for pipeline tools) (example: `<your-project-id>`)
Note: Also available via uv local install. Docker image recommended.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.ZENML_STORE_URLrequiredURL of the ZenML server to connect toZENML_STORE_API_KEYrequiredAPI key/token used to authenticate with the ZenML serverZENML_ACTIVE_PROJECT_IDrequiredActive project ID required for pipeline run tools and MCP appsMCP server that exposes GraphQL operations as tools for AI models.