You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The MCP Gateway configuration requires domains to follow a specific DNS hostname pattern (regex: ^[a-zA-Z0-9]([a-zA-Z0-9\\-]{0,61}[a-zA-Z0-9])?(\\.[a-zA-Z0-9]([a-zA-Z0-9\\-]{0,61}[a-zA-Z0-9])?)*$), but this requirement is completely undocumented in the user-facing documentation.
Users encounter validation errors without understanding the format requirements, leading to frustration and support requests.
Suggested Changes
Add a "Domain Format Requirements" section to docs/src/content/docs/reference/mcp-gateway.md:
### Domain Format Requirements
MCP Gateway domains must be valid DNS hostnames following these rules:
- Start and end with alphanumeric characters (a-z, A-Z, 0-9)
- May contain hyphens (-) in the middle
- Each label (part between dots) must be 1-63 characters
- No consecutive dots or trailing dots
- No underscores or other special characters
**Valid Examples:**-`api.example.com`-`localhost`-`mcp-server.internal`-`my-service.company.io`**Invalid Examples:**-`-invalid.com` (starts with hyphen)
-`domain..com` (consecutive dots)
-`under_score.com` (contains underscore)
-`trailing-hyphen-.com` (ends with hyphen)
Files Affected
docs/src/content/docs/reference/mcp-gateway.md
Success Criteria
Domain pattern requirements documented with clear examples
Valid and invalid examples provided
No changes to validation logic needed (already enforced in schema)
Activity
github-actions commentedon Feb 8, 2026
🍪 Issue Monster has assigned this to Copilot!
I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot agent.
The Copilot agent will analyze the issue and create a pull request with the fix.
Om nom nom! 🍪
github-actions commentedon Feb 9, 2026
This issue was automatically closed because it expired on 2026-02-09T05:26:24.181Z.