Uh oh!
There was an error while loading. Please reload this page.
feat(mcp): CNAMEs and wildcard Access app for per-backend MCP endpoints - #27
Merged
Conversation
OpenTofu Plan |
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
What
Adds edge prerequisites for per-backend MCP endpoints behind the existing cluster-apps tunnel:
cf-tunnels.tf: 9 new CNAMEs undermcp.makeitwork.cloud— apify, argocd-makeitwork, aws-docs, context7, github, grafana-makeitwork, kubernetes, parallel-search, terraform-docs. The aggregate VirtualMCPServer stays at the baremcphostname.cf-access-mcp.tf: new Access applicationmcp_gateway_backendscovering*.mcp.makeitwork.cloud, reusing the existingmcp-gatewayservice token (non_identity policy) plus the admins group policy.Why: MCP clients get one config entry per integration with natural tool names, instead of one aggregate entry with gateway-prefixed tools.
Ordering constraint (per AGENTS.md)
This must apply before the matching TunnelBinding subjects merge in kustomize-cluster (commit ready, held locally). If cloudflare-operator creates the DNS records first, this apply fails with 81053 and records would need importing.
After merge
Verify CNAMEs exist → push kustomize-cluster TunnelBinding → push client config repos.
Verified: terraform fmt clean, terraform validate passing, terraform-docs README updated by hook.