Skip to content

[docs][MCP] Document simplified ingress for Retool 4.0.7+ #351

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
arnold-retool merged 2 commits into from
Jul 23, 2026
Merged

[docs][MCP] Document simplified ingress for Retool 4.0.7+ #351

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5975b2d
[docs][MCP] Document simplified ingress for 4.0.7
arnold-retool Jul 23, 2026
6c33de1
[docs][MCP] Keep chart version unchanged
arnold-retool Jul 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 15 additions & 2 deletions charts/retool/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -731,8 +731,21 @@ mcp:
annotations: {}
labels: {}

# Public MCP routes, rendered before the main Retool route. External ingress
# must preserve this order and target mapping:
# Retool 4.0.7 and later support a simplified ingress setup: route all public
# paths, including /mcp and /.well-known, to the main Retool Service on port
# 3000. The main backend must also be able to relay /mcp to the in-cluster MCP
# Service. Set its internal URL through the top-level env block:
#
# env:
# MCP_SERVICE_INGRESS_DOMAIN: http://<fullname>-mcp:4010
#
# With that backend setting, omit or disable the MCP-specific ingress or
# HTTPRoute rules below and keep only the normal "/" route to
# <fullname>:3000. Replace <fullname> with this chart release's full name.
#
# Retool versions before 4.0.7 require the explicit MCP routes below,
# rendered before the main Retool route. External ingress must preserve this
# order and target mapping:
# Exact /.well-known/oauth-authorization-server -> <fullname>-backend-internal:3001
# Exact /.well-known/oauth-protected-resource -> <fullname>-mcp:4010
# Prefix /mcp -> <fullname>-mcp:4010
Expand Down
17 changes: 15 additions & 2 deletions values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -731,8 +731,21 @@ mcp:
annotations: {}
labels: {}

# Public MCP routes, rendered before the main Retool route. External ingress
# must preserve this order and target mapping:
# Retool 4.0.7 and later support a simplified ingress setup: route all public
# paths, including /mcp and /.well-known, to the main Retool Service on port
# 3000. The main backend must also be able to relay /mcp to the in-cluster MCP
# Service. Set its internal URL through the top-level env block:
#
# env:
# MCP_SERVICE_INGRESS_DOMAIN: http://<fullname>-mcp:4010
#
# With that backend setting, omit or disable the MCP-specific ingress or
# HTTPRoute rules below and keep only the normal "/" route to
# <fullname>:3000. Replace <fullname> with this chart release's full name.
#
# Retool versions before 4.0.7 require the explicit MCP routes below,
# rendered before the main Retool route. External ingress must preserve this
# order and target mapping:
# Exact /.well-known/oauth-authorization-server -> <fullname>-backend-internal:3001
# Exact /.well-known/oauth-protected-resource -> <fullname>-mcp:4010
# Prefix /mcp -> <fullname>-mcp:4010
Expand Down
Loading