fix: correct MCP server path and invocation

Fix MCP server startup failures by using correct dist/ path and node invocation.

Changes:
- Dockerfile.b00t: Update symlink to dist/plantuml-mcp-server.js (not bin/)
- supervisord.conf: Use 'node /path/to/plantuml-mcp-server.js' instead of command name

Fixes: supervisord error 'can't find command plantuml-mcp-server'

Author: elasticdotventures

Dockerfile.b00t

@@ -56,8 +56,9 @@ COPY --from=mcp-builder /usr/local/lib/node_modules/plantuml-mcp-server \
     /usr/local/lib/node_modules/plantuml-mcp-server
 
 # Create symlink for MCP server binary
-RUN ln -s /usr/local/lib/node_modules/plantuml-mcp-server/bin/plantuml-mcp-server \
-    /usr/local/bin/plantuml-mcp-server
+RUN ln -s /usr/local/lib/node_modules/plantuml-mcp-server/dist/plantuml-mcp-server.js \
+    /usr/local/bin/plantuml-mcp-server && \
+    chmod +x /usr/local/bin/plantuml-mcp-server
 
 # Copy supervisord configuration
 COPY supervisord.conf /etc/supervisord.conf

supervisord.conf

@@ -18,7 +18,7 @@ stderr_logfile_maxbytes=0
 priority=100
 
 [program:mcp-server]
-command=plantuml-mcp-server
+command=node /usr/local/lib/node_modules/plantuml-mcp-server/dist/plantuml-mcp-server.js
 directory=/opt/mcp
 autostart=true
 autorestart=true