# Reported issues for mcp-zenml

Pod holds 6 of 6 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [mcp-zenml](/mcp/mcp-zenml).

## Most discussed

### occasional incorrect shutdown, pinning CPU to 100%

ZenML MCP server was slowly consuming all my cpus. it spawns a `zenmldocker/mcp-zenml` container using `docker run`.
when agent session ends, this container is not removed (at least on claude-code). And according to fable, stdio MCP servers whose stdin closed, get continuous EOF and busy-loop instead of exiting, pinning that proc to 100%

This aggregated over multiple weeks, during which I certainly had more agent sessions than cpu cores, so I presume it's flaky behaviour to some extent.

[Read the thread](https://github.com/zenml-io/mcp-zenml/issues/66) · 2026-08-03 · open · external user · 0 comments

### Artifact version commands

I was building a use-case which needed to extract schema from artifacts. I therefore added the `get_artifact_version` and `list_artifact_versions` tools in the ZenML MCP.

You can find the PR here #30

[Read the thread](https://github.com/zenml-io/mcp-zenml/issues/31) · 2026-01-26 · closed · outside contributor · 0 comments

### Claude Desktop extension feedback

Hi from Anthropic! Thanks for your submission to the Claude Desktop extension registry.

Could you update manifest.json should list all tools in the MCP server and re-submit via the interest [form](https://docs.google.com/forms/d/e/1FAIpQLScHtjkiCNjpqnWtFLIQStChXlvVcvX8NPXkMfjtYPDPymgang/viewform?usp=header)?

Also, we've updated the [spec](https://github.com/anthropics/mcpb) to request any `privacy_policies` be included in manifest.json

Many thanks!

[Read the thread](https://github.com/zenml-io/mcp-zenml/issues/21) · 2025-09-17 · closed · external user · 1 comment

### 🚨 MCP Smoke Test Failed

## MCP Smoke Test Failure Report

The automated MCP smoke test has failed. This indicates there may be issues with the MCP server functionality.

### Details

**Workflow Run:** [6](https://github.com/zenml-io/mcp-zenml/actions/runs/16070126273)
**Branch:** refs/heads/main
**Commit:** 4298480
**Triggered by:** schedule
**Date:** 2025-07-04T09:11:12.591Z

### Investigation Steps

1. Check the [workflow logs](https://github.com/zenml-io/mcp-zenml/actions/runs/16070126273) for detailed error informa

[Read the thread](https://github.com/zenml-io/mcp-zenml/issues/10) · 2025-07-04 · closed · external user · 0 comments

### 🚨 MCP Smoke Test Failed

## MCP Smoke Test Failure Report

The automated MCP smoke test has failed. This indicates there may be issues with the MCP server functionality.

### Details

**Workflow Run:** [1](https://github.com/zenml-io/mcp-zenml/actions/runs/15804956928)
**Branch:** refs/heads/main
**Commit:** 22a80ce
**Triggered by:** schedule
**Date:** 2025-06-22T09:04:51.924Z

### Investigation Steps

1. Check the [workflow logs](https://github.com/zenml-io/mcp-zenml/actions/runs/15804956928) for detailed error informa

[Read the thread](https://github.com/zenml-io/mcp-zenml/issues/5) · 2025-06-22 · closed · external user · 0 comments

### Glama listing is missing Dockerfile

Your MCP server is currently listed on the [Glama MCP directory](https://glama.ai/mcp/servers/zenml-io/mcp-zenml), but it is not available for others to use because it does not have a Dockerfile.

It takes only a few minutes to fix this:

1. Go to your server's listing: [zenml-io/mcp-zenml](https://glama.ai/mcp/servers/zenml-io/mcp-zenml)
2. Click "Claim" to verify ownership.
3. Once claimed, navigate to the [admin `Dockerfile` page](https://glama.ai/mcp/servers/zenml-io/mcp-zenml/admin/dockerfi

[Read the thread](https://github.com/zenml-io/mcp-zenml/issues/2) · 2025-04-23 · closed · external user · 3 comments

## Most recent

The remaining reports are on [the project's issue tracker](https://github.com/zenml-io/mcp-zenml/issues).