Repository navigation
feat: support BYOC tunnel bindings for MCP requests - #42
Merged
Merged
Conversation
9 tasks done
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.
Summary
Expose the optional top-level
tunnel_idfor BYOC MCP routing. Callers can bind a Managed Session at creation, or configure a Managed Deployment or Forward Template so its sessions inherit the tunnel. For Deployment and Template updates, omitting the field keeps the binding, a new ID replaces it, and JSONnullclears it. Both resource models expose the configured tunnel ID.Verification
On Node 22, 4,461 offline tests passed. The public types compiled, including a negative check for a numeric tunnel ID. The docs check and npm pack dry run also passed. The wire tests cover serialization and response decoding. End-to-end MCP routing through a live BYOC tunnel is pending QA.