trigger_pipeline
Trigger a pipeline run (prefer snapshotnameorid parameter)
How to use it
Project documentation lists trigger_pipeline for the MCP Zenml MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.
Install MCP Zenml
npx cloudflared tunnel --url http://localhost:8001Other tools in MCP Zenml (22)
Diagnose server setup (env vars, SDK, connectivity, auth). Works even when misconfigured.
Get the currently active project
Get build details (image, code embedding)
Get a deployment's runtime status and URL
Get bounded logs from a deployment (tail=100 default, max 1000)
Get project details by name/ID
Use getsnapshot instead
Get a frozen pipeline configuration by name/ID
Get tag details (exclusive, colors)
Artifact metadata
List builds with filters (islocal, containscode)
List deployments with filters (status, pipeline, tag)
List all projects
Use listsnapshots instead
Secret names (not values)
List snapshots with filters (runnable, deployable, deployed, tag)
List tags with filters (resourcetype)
Get N most recent runs
Open interactive pipeline runs dashboard (MCP App)
Open 30-day run activity bar chart (MCP App)
Analyze recent pipeline runs
Analyze stack component usage