FreeOnePlus opened a new pull request, #93: URL: https://github.com/apache/doris-mcp-server/pull/93
## What changed - upgrade the Python MCP SDK dependency to 2.0.x - add one shared low-level protocol factory for tools, resources, and prompts - migrate Streamable HTTP and STDIO to the SDK 2.0 dual-era runner - keep modern `2026-07-28` and legacy `2025-11-25` clients interoperable - make modern HTTP stateless and share the same handlers in single- and multi-worker modes - migrate the packaged client to the SDK 2.0 high-level client - reject query-string bearer tokens and tighten default Host/Origin handling - add the protocol audit, implementation ledger, regression tests, and wheel packaging fix ## Why The previous implementation was pinned to SDK 1.x and depended on duplicated handlers and private transport monkey patches. It could not complete a `2026-07-28` `server/discover` request and the process exited after the failure. This PR establishes the protocol core required for the 2026-07-28 migration without claiming that the remaining conformance and security ledger is complete. ## Validation - `uv run pytest -q`: 331 passed, 57 skipped, 0 failed - protocol regression: modern and legacy list/call/read/get paths passed - Streamable HTTP: modern and legacy requests passed against a real Doris 4.0.5 environment - STDIO: modern and legacy requests passed against the same real Doris environment - multi-worker HTTP: two worker processes both served successful real Doris requests - external SQL injection API suite: 45 passed - `uv lock --check`, scoped Ruff, `compileall`, and `git diff --check` passed - `uv build` produced sdist and wheel - clean wheel install: both `doris-mcp-server --help` and `doris-mcp-client --help` passed ## Follow-up The development ledger intentionally leaves official conformance, missing-capability `-32021`, typed Resource/Prompt errors, non-loopback fail-closed authentication, and the remaining security/release gates for separate PRs. -- 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]
