-
Notifications
You must be signed in to change notification settings - Fork 607
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
- Status: Open.#1175 In modelcontextprotocol/rust-sdk;
- Status: Open.#1174 In modelcontextprotocol/rust-sdk;
- Status: Open.#1172 In modelcontextprotocol/rust-sdk;
Elicitation
requestedSchemasilently drops$schemaand unknown property keywordsbugSomething is not workingSomething is not workingStatus: Open.#1168 In modelcontextprotocol/rust-sdk;- Status: Open.#1164 In modelcontextprotocol/rust-sdk;
request-state and JWT signing key material lacks minimum-length enforcement and zeroization
bugSomething is not workingSomething is not workingStatus: Open.#1161 In modelcontextprotocol/rust-sdk;stdio server: malformed-_meta 2026 request as first message gets no error response (connection wedges silently)
bugSomething is not workingSomething is not workingP1High: significant functionality gap or spec violationHigh: significant functionality gap or spec violationready for workIssue is well-defined and ready to be picked upIssue is well-defined and ready to be picked upT-serviceService layer changesService layer changesT-transportTransport layer changesTransport layer changesStatus: Open.#1157 In modelcontextprotocol/rust-sdk;public API naming and shape decisions drift without a referenced style guide
P3Low: nice-to-have, long-term, or exploratoryLow: nice-to-have, long-term, or exploratoryquestionFurther information is requestedFurther information is requestedT-documentationDocumentation improvementsDocumentation improvementsT-enhancementNew features and enhancementsNew features and enhancementsStatus: Open.#1155 In modelcontextprotocol/rust-sdk;examples/servers/src/mrtr.rsnever checks the elicitationaction, so a declined elicitation is answered as if it had been acceptedbugSomething is not workingSomething is not workingP1High: significant functionality gap or spec violationHigh: significant functionality gap or spec violationready for workIssue is well-defined and ready to be picked upIssue is well-defined and ready to be picked upT-examplesExample code changesExample code changesStatus: Open.#1147 In modelcontextprotocol/rust-sdk;Should ServiceExt::serve() return after initialization?
needs reproBug report that needs a minimal reproduction caseBug report that needs a minimal reproduction caseP3Low: nice-to-have, long-term, or exploratoryLow: nice-to-have, long-term, or exploratoryquestionFurther information is requestedFurther information is requestedT-serviceService layer changesService layer changesStatus: Open.#1143 In modelcontextprotocol/rust-sdk;SEP-2260 follow-up: skip session tracking and the standalone GET stream at protocol >= 2026-07-28
enhancementNew feature or requestNew feature or requestP2Medium: important but non-blocking improvementMedium: important but non-blocking improvementT-transportTransport layer changesTransport layer changesStatus: Open.#1108 In modelcontextprotocol/rust-sdk;rs1.request-state format carries nokid, so key rotation cannot be targetedP2Medium: important but non-blocking improvementMedium: important but non-blocking improvementStatus: Open.#1096 In modelcontextprotocol/rust-sdk;