FreeOnePlus opened a new pull request, #94:
URL: https://github.com/apache/doris-mcp-server/pull/94

   ## Dependency
   
   Stacked on #93. The incremental change for this PR is commit `6b5c779`; the 
shared protocol-core diff will disappear after #93 lands.
   
   ## What changed
   
   - add an optional per-method required-client-capability policy to the shared 
protocol factory
   - return MCP `-32021` with typed `requiredCapabilities` data when a modern 
request lacks a declared requirement
   - keep legacy requests outside the 2026-era capability gate
   - test required `_meta`, missing capabilities, unsupported versions, and 
recovery after errors
   
   ## Why
   
   MCP 2026-07-28 requires every request to carry its protocol version and 
client capabilities. When a handler requires a capability that the request did 
not declare, the server must return `MissingRequiredClientCapability` 
(`-32021`). The Doris handlers currently require no extra capabilities by 
default, so the gate is opt-in per method and does not invent a requirement for 
existing tools.
   
   ## Validation
   
   - HTTP missing `clientCapabilities`: `-32602`
   - HTTP missing a configured extension: `-32021`
   - HTTP with the required extension: success
   - real subprocess STDIO missing the extension: `-32021`
   - real subprocess STDIO unsupported version: `-32022` with `supported` and 
`requested`
   - HTTP and STDIO both accept a valid request after the error
   - legacy STDIO remains compatible
   - protocol test file: 5 passed
   - full suite: 333 passed, 57 skipped, 0 failed
   - scoped Ruff, `compileall`, `uv lock --check`, `uv build`, and `git diff 
--check` passed
   
   ## Known follow-up
   
   The existing query-cache cleanup task can remain pending at interpreter 
shutdown in some full-suite runs. It is tracked separately as `TEST-011` and is 
intentionally not mixed into this protocol PR.
   


-- 
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]

Reply via email to