Repository navigation
Harden MCP transport and simplify client lifecycle - #4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Local HTTP MCP now uses a per-user bearer credential and checks Host/Origin, while blocking editor operations run outside the server event loop. The standalone stdio bridge reads the current port credential for each request, so an existing client can continue after a same-port server restart without importing the engine. A completed CLI response is emitted before disconnect cleanup can fail.
The SDK server uses its public stateless HTTP lifecycle. Missing grants do not silently permit every capability, malformed client configuration is preserved, and invalid session names are rejected at the filesystem boundary. Documentation describes the trusted-development boundary and the actual limits of Undo.
Validation: real authentication/Host/Origin HTTP probes, HTTP and stdio requests, health during a slow call, and restart with the same stdio client; client transport tests passed locally. Engine-side integration is covered by Infernux PR #90. No version bump, tag or release publication.