Support host-specific _meta.ui.domain with auto-computed defaults#22
Merged
Support host-specific _meta.ui.domain with auto-computed defaults#22
Conversation
Add domain resolution that maps clientInfo.name to host-specific sandbox domains. Resources can declare a domain map (keyed by host name with a default fallback) or a plain string. Both dev and production servers resolve the map after MCP initialization and update listing-level _meta so hosts like ChatGPT see the domain in resources/list. When resources don't set a domain, the server auto-computes one from the server URL for known hosts (openai-mcp, chatgpt-*, claude), eliminating the "Widget domain is not set" warning in ChatGPT out of the box.
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
resolve-domain.tswith domain resolution: mapsclientInfo.nameto host-specific sandbox domains (string orRecord<host, domain>withdefaultfallback)openai-mcp,chatgpt-*,claude) so the ChatGPT "Widget domain is not set" warning doesn't appear out of the box_metaviaRegisteredResource.update()soresources/listincludes the domainserverUrloption toProductionServerConfigandWebHandlerConfigfor production auto-computationResourceConfigtype to acceptDomainConfig(string or map) for thedomainfieldTest plan
pnpm --filter sunpeak validatepasses (typecheck, lint, 233 tests, build)sunpeak dev→ connect from ChatGPT → verify domain appears in resource metadata and warning is gone