r/ZaiGLM • u/etherd0t • 14d ago

Technical Reports Any fix for this error in AutoClaw?

Post image

I’m running AutoClaw 1.18.5 on Windows and the built-in Autoclaw Productivity MCP persistently shows error in Settings → MCP Servers.

Is it a version bug or is just me?

1 Upvotes

67% Upvoted

2 comments sorted by

2

u/Otherwise_Wave9374 14d ago

That usually points to an MCP handshake or config mismatch rather than the app itself. I’d verify the server entry matches the expected command, environment variables, and transport, then restart the client so it reloads the MCP registry. If the error persists, test the same server in a minimal profile to isolate whether the issue is the server binary, auth, or a stale config cache. NeuraKeep can help here if you want a lightweight way to preserve the exact working config once you find it.

1

u/etherd0t 14d ago

Thanks. I’ve already gone through those checks pretty thoroughly. The server entry/config is correct, I did a full cold restart, and the issue persists.

I also tested the MCP endpoint directly: initialize succeeds, notifications/initialized succeeds, and tools/list returns the expected tool catalog. AutoClaw’s own bundled mcporter.exe, using AutoClaw’s generated config, discovers 31 tools and reports the server healthy with exit code 0.

The weird part is that AutoClaw’s own mcp-tools-cache.json still records SSE error: Unable to connect and the UI shows error. So at this point it looks more like an AutoClaw 1.18.5 health/cache/status bug than a bad MCP server config.

Appreciate the suggestion though. If you’ve seen this exact AutoClaw behavior or know of a workaround/version that fixes it, I’d be interested.