fix(mcp): derive gateway WebSocket URL from template port - #351
Open
Aphroq wants to merge 1 commit into
Open
Conversation
Contributor License Agreement ✅All contributors have signed the CLA. Thank you! |
Aphroq
force-pushed
the
fix/mcp-gateway-websocket-url
branch
from
August 25, 2026 00:14
d44282b to
0e081bf
Compare
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
1 participant
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
Pass the generated API Gateway address explicitly to the optional MCP server in template 2.8.
TrustGraph 2.8 changed the MCP server built-in gateway default to ws://api-gateway:8888/api/v1/socket, while the 2.8 deployment template still starts and exposes the API Gateway on configurable port 8088. Generated deployments therefore start successfully but the MCP server connects to the wrong internal port when its first tool is invoked.
Template 2.7 is not changed because its MCP server default is already 8088.
Changes
No new configuration field or hard-coded duplicate port is introduced.
Validation
The test builds a full 2.8 Compose resource graph and asserts that the API Gateway port and MCP Server WebSocket URL resolve from the same configured value.