Troubleshooting

no caproni.yaml found in current directory or any parent directory up to home directory

The server started somewhere without a config above it. The message says caproni.yaml because the string hasn’t been renamed; xianyun.yaml works too. Start xianyun-mcp in your project directory, or set your client’s working-directory option.

middleware asked the client for input, which requires MCP protocol 2026-07-28 or newer

You called a gated tool from a client that negotiated an older protocol, or one that doesn’t declare elicitation. The command didn’t run. Run the matching xianyun command in a terminal.

The tools don’t show up

Run the server yourself and list what it exports:

$ xianyun-mcp mcp tools
$ head mcp-tools.json

If that works, the problem is in your client’s config. Confirm the command is on the PATH your client uses, which can differ from your shell’s.

A command works in a terminal and fails over MCP

The server runs with the environment and working directory your client gave it. Differences in PATH, HOME, KUBECONFIG, or DOCKER_HOST change results. Run xianyun_doctor through MCP and compare it with the terminal.

xianyun_up fails with an unknown deployer type

The type must be helm, kustomize, or namespace. Any other value fails validation, and nix is a placeholder module with no manager behind it.

Output looks wrong

xianyun_ca_inspect prints dates as Some(SystemTime { ... }), and xianyun version says “caproni”. Both are known (GAP-008) and don’t indicate a broken install.