typescript-sdk

I've updated to 1.25.1, and I get ../../node_modules/@modelcontextprotocol/sdk/dist/esm/server/streamableHttp.d.ts:58:22 - error TS2420: Class 'StreamableHTTPServerTransport' incorrectly implements interface 'Transport'. Types of property 'onclose' are incompatible. Type '(() => void) | undefined' is not assignable to type '() => void'. Type 'undefined' is not assignable to type '() => void'. 58 export declare class StreamableHTTPServerTransport implements Transport { ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Found 1 error. I suspect this is due to "exactOptionalPropertyTypes": true in my tsconfig.json.

Motivation and Context Tools, prompts, resources and resource templates registered on can all be toggled with /. A disabled one drops out of its list verb and is rejected when invoked. #247 added this for all four primitives at once. Resource templates are the exception.** has the field and does flip it, but none of these four handlers read it. As a result, a disabled resource template is still exposed in the four responses above. In order to fix, the missing check at all four sites, in two shapes: and filter disabled templates out. Nothing was addressed specifically, so there is nobody to report a failure to. and throw , since the client named a specific resource template. How Has This Been Tested? Four tests in , one per request path, each committed ahead of its fix so it can be checked red → green. : a disabled static resource and a disabled template drop out, the enabled template stays : the disabled template's URI pattern is gone : a URI matching a disabled template is rejected with + : a completion aimed at a disabled template is rejected the same way The first testcase() also covers the static-resource filtering. That already worked, but it sits in the same handler as the template path, so pinning it down keeps a fix on one side from breaking the other. Breaking Changes No API change. Types of changes [x] Bug fix (non-breaking change which fixes an issue) [ ] New feature (non-breaking change which adds functionality) [ ] Breaking change (fix or feature that would cause existing functionality to change) [ ] Documentation update Checklist [x] I have read the MCP Documentation [x] My code follows the repository's style guidelines [x] New and existing tests pass locally [x] I have added appropriate error handling [ ] I have added or updated documentation as needed Additional context For I went with throwing, following the disabled prompt case. The branch below in the same handler returns for static resources. If that's the better fit here, I'm happy to change it. Let me know. fixes: #2696