Image build v0.1.2 not operational

[flrichar]

I noticed if I used latest as in the most-recent git commit from the upstream project, it breaks my Liz/Rancher integration. Unsure why at the moment.

• v0.1.2 has latest code, but broken
• v0.1.1 still works correctly
• changed build to include --no-cache, checksum changed but still same error from Rancher AI assistant integration

Evaluating different mcp testing tools like mcptools (golang) and modelcontextprotocol/inspector (node.js).

[flrichar]

This has to do with the roots requested from the client, its not falling back to the current working directory. Built latest image with the latest commit as of 2026-0403, for image tag v0.1.3. Still using v0.1.1 in simple deployments. Continued testing and evaluation. Perhaps look at the tests for that option, main_test.go.

[flrichar]

It is due to the roots/list feature in the newer builds.

Gemini said:

This is a classic "bleeding-edge" trap when pulling from the main branch of an actively developed open-source repository. You haven't done anything wrong with your Kubernetes configuration; the Go binary's underlying logic has actually fundamentally changed under the hood in the last few days.

There are two distinct updates to mcp-taskfile-server that are colliding with your Kubernetes lab setup. Here is exactly why it is suddenly missing the default root, and how to fix it.

1. The New roots/list Protocol Update (The Likely Culprit)

In the older builds you were testing, the mcp-taskfile-server blindly trusted whatever directory it was launched in. It looked at the Kubernetes workingDir, found the file, and exposed the tools.

However, the author recently implemented Multi-Root Prefixing using the official MCP roots/list capability.

The New Behavior: After the initial handshake, the Go binary now actively asks the AI Client (Rancher AI): "What directories do you want me to load Taskfiles from?"

The Disconnect: Because Rancher AI is a cloud-based client, it doesn't know about your local container paths like /app/custom-tasks. If Rancher (or the proxy) advertises that it supports the "roots" feature but returns an empty array [], the Go binary says, "Ah, the client gave me 0 roots to load" and completely ignores your local Kubernetes working directory. It only falls back to the local directory if the client explicitly states it does not support roots.

...