Title: Investigate migration to stateless MCP 2026-07-28 · Issue #293 · devframes/devframe · GitHub
Open Graph Title: Investigate migration to stateless MCP 2026-07-28 · Issue #293 · devframes/devframe
X Title: Investigate migration to stateless MCP 2026-07-28 · Issue #293 · devframes/devframe
Description: Context While reviewing the resource subscription work in PR #292, we noticed that Devframe still uses the 2025-era MCP protocol model. Devframe already depends on version 2 of the TypeScript MCP SDK, but the SDK keeps hand-constructed c...
Open Graph Description: Context While reviewing the resource subscription work in PR #292, we noticed that Devframe still uses the 2025-era MCP protocol model. Devframe already depends on version 2 of the TypeScript MCP S...
X Description: Context While reviewing the resource subscription work in PR #292, we noticed that Devframe still uses the 2025-era MCP protocol model. Devframe already depends on version 2 of the TypeScript MCP S...
Opengraph URL: https://github.com/devframes/devframe/issues/293
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Investigate migration to stateless MCP 2026-07-28","articleBody":"## Context\n\nWhile reviewing the resource subscription work in [PR #292](https://github.com/devframes/devframe/pull/292), we noticed that Devframe still uses the 2025-era MCP protocol model.\n\nDevframe already depends on version 2 of the TypeScript MCP SDK, but the SDK keeps hand-constructed clients and servers on the legacy protocol unless applications opt into the new serving and negotiation entry points.\n\nThe current Devframe implementation still relies on:\n\n- the `initialize` handshake\n- `Mcp-Session-Id`\n- session-local HTTP routing\n- GET and DELETE session operations\n- `resources/subscribe` and `resources/unsubscribe`\n- direct `Server.connect()` calls for stdio\n- legacy client negotiation in `devframe connect`\n\nMCP 2026-07-28 replaces this with a stateless protocol based on independent requests, per-request metadata, `server/discover`, and `subscriptions/listen`.\n\nReferences:\n\n- [MCP 2026-07-28 specification](https://modelcontextprotocol.io/specification/2026-07-28)\n- [TypeScript SDK migration guide](https://github.com/modelcontextprotocol/typescript-sdk/blob/main/docs/migration/support-2026-07-28.md)\n\n## Why consider migrating\n\nThe stateless model is now the direction of the MCP specification. Existing 2025-era behavior remains supported for compatibility, but newer protocol work and client behavior will build on the 2026 model.\n\nUnless Devframe intentionally remains a legacy-only MCP implementation, we will likely need to migrate at some point to maintain compatibility with modern MCP clients and future protocol revisions.\n\nMigration would bring:\n\n- modern MCP client compatibility\n- HTTP requests that can reach any server instance without session affinity\n- no application-owned `Mcp-Session-Id` registry or DELETE teardown protocol\n- SDK-managed protocol discovery and per-request version validation\n- SDK-managed `subscriptions/listen` routing and notification filtering\n- required HTTP routing-header validation\n- automatic modern result fields such as `resultType`, `ttlMs`, and `cacheScope`\n- one server factory that can serve both protocol eras where compatibility is needed\n- a clearer path to future MCP extensions built on the stateless protocol\n\nThis should also let Devframe delete part of its custom HTTP session lifecycle once legacy support is no longer needed.\n\n## Likely migration cost\n\nThis is more than changing a protocol-version constant.\n\nThe server construction model would need to change from a session-owned server to an SDK factory:\n\n- HTTP would move to `createMcpHandler`.\n- Stdio would move to `serveStdio`.\n- `devframe connect` would enable modern version negotiation.\n- MCP server registration would need to work when the SDK creates instances per request or connection.\n\nResource notifications need particular attention. MCP 2026-07-28 replaces `resources/subscribe` and `resources/unsubscribe` with a long-lived `subscriptions/listen` request. Devframe would need to:\n\n- publish resource and list changes through the SDK notification bus\n- decide how the existing resource `subscribe` and `unsubscribe` callbacks map to listen-stream lifecycle\n- preserve correct cleanup when a listen stream closes\n- update the SharedState resource bridge\n- test concurrent listeners and resource-specific filters\n\nCompatibility policy changes the size of the work:\n\n- A modern-only migration could replace the custom HTTP session handler.\n- Supporting both eras would require routing modern requests to `createMcpHandler` while retaining the current sessionful handler for legacy clients. The SDK's default legacy HTTP fallback is stateless and cannot preserve legacy resource subscriptions by itself.\n- Tests would need separate modern and legacy coverage. Current raw HTTP and in-memory tests exercise the legacy handshake.\n- Documentation would need to explain the supported protocol versions and any legacy compatibility window.\n\nThe public Devframe resource API may remain useful, but its subscription semantics should be reviewed before treating the current callback lifecycle as the long-term contract.\n\n## Questions\n\n- Should Devframe adopt MCP 2026-07-28 now, or wait for broader client adoption?\n- Should the first migration support both protocol eras or move directly to modern-only MCP?\n- If legacy support remains, how long should Devframe keep the sessionful HTTP route?\n- Should HTTP, stdio, and `devframe connect` migrate together?\n- How should Devframe's resource subscription callbacks map to `subscriptions/listen`?\n- Can the migration preserve the current public resource API, or should subscription lifecycle become an internal MCP adapter concern?\n","author":{"url":"https://github.com/dvcolomban","@type":"Person","name":"dvcolomban"},"datePublished":"2026-08-25T18:45:51Z","url":"https://github.com/devframes/devframe/issues/293"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react-reconciler,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@d5750093facf |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:f3939a21-1d69-42b6-9a53-931c954ec5cc |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 99FE:4E2A2:108705:1725C0:6AFB6ACE |
| html-safe-nonce | 6b809a897b92fff7c6ebd41b6179b9ceaf835be3deec11371feadfb1679d4a39 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5OUZFOjRFMkEyOjEwODcwNToxNzI1QzA6NkFGQjZBQ0UiLCJ2aXNpdG9yX2lkIjoiMzMzNDczODEzOTQxODQyMTk2NiIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | d7f8a1aada4fb64e3f0802fe79989dc954dbb6bd687bbd82ecc93661ec184ab9 |
| hovercard-subject-tag | issue:5249370316 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/devframes/devframe/293/issue_layout |
| twitter:image | https://opengraph.githubassets.com/f682fa20e569ddc3b8e11fc919070d47ce76986b98a56fe3fcb85562178e31e8/devframes/devframe/issues/293 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/f682fa20e569ddc3b8e11fc919070d47ce76986b98a56fe3fcb85562178e31e8/devframes/devframe/issues/293 |
| og:image:alt | Context While reviewing the resource subscription work in PR #292, we noticed that Devframe still uses the 2025-era MCP protocol model. Devframe already depends on version 2 of the TypeScript MCP S... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | dvcolomban |
| hostname | github.com |
| expected-hostname | github.com |
| None | cca289ecd54650fcf3c0b037a58b97186dee2cc4406819d87fab93728fd83700 |
| turbo-cache-control | no-preview |
| go-import | github.com/devframes/devframe git https://github.com/devframes/devframe.git |
| octolytics-dimension-user_id | 279879373 |
| octolytics-dimension-user_login | devframes |
| octolytics-dimension-repository_id | 1231722386 |
| octolytics-dimension-repository_nwo | devframes/devframe |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 1231722386 |
| octolytics-dimension-repository_network_root_nwo | devframes/devframe |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 88808b1fae5ab8a526a73e7ce5542a10eb9d6971 |
| ui-target | canary-2 |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width