FreeOnePlus opened a new pull request, #132: URL: https://github.com/apache/doris-mcp-server/pull/132
## Summary - publish one MCP listener on container port 3000 and move Grafana to host port 3003 by default - make the image liveness probe use `/live` and the Compose readiness probe use `/ready` on the real listener - wait for healthy Doris FE/BE services before starting MCP and wait for MCP readiness before nginx - keep the Docker build context and runtime image limited to explicit runtime files - propagate explicit MCP Host/Origin allowlists for single- and multi-worker HTTP deployments - regenerate the container dependency manifest from `pyproject.toml` so the image uses MCP SDK 2.0 ## Root cause The Compose file published unused MCP ports, pointed its health check at an inactive port, and conflicted with Grafana on host port 3000. The image-level probe also used the compatibility health endpoint, the Docker build copied the whole repository, and the generated requirements file still selected MCP SDK 1.x. ## Impact The default deployment now has unique host ports, a single real MCP listener, separate liveness/readiness semantics, fail-closed deployment Host validation, and a smaller production image that does not receive local reports, tests, or source-control metadata. ## Validation - `uv run pytest -q`: 616 passed, 64 skipped - focused deployment/protocol/health suite: 40 passed - real Doris transport suite: 7 passed across Streamable HTTP and true subprocess Stdio - unavailable Doris container: `/live` 200, `/ready` 503, Docker health healthy - real Doris container: Compose-style readiness healthy and Streamable HTTP `exec_query` returned 1 - `docker compose config --quiet` - `uv lock --check`, requirements consistency, Ruff, Bandit, shell syntax, compileall, and `uv build` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
