Skip to content

feat(mcp): expose the gateway as mcp.makeitwork.cloud - #64

Merged
xnoto merged 1 commit into
mainfrom
feat/mcp-gateway-tunnel
Aug 26, 2026
Merged

feat(mcp): expose the gateway as mcp.makeitwork.cloud#64
xnoto merged 1 commit into
mainfrom
feat/mcp-gateway-tunnel

Conversation

@xnoto

@xnoto xnoto commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Follow-up to #62 as planned: TunnelBinding mcp.makeitwork.cloudhttp://vmcp-gateway.mcp.svc:4483.

Sequencing verified before opening:

  • mcp CNAME applied via tfroot-cloudflare#26 (no 81053 race)
  • Access app live: unauthenticated GET https://mcp.makeitwork.cloud/mcp → 302 to Access login
  • vMCP healthy: tools/list via port-forward returns 16 aggregated tools (context7×2, kubernetes×14)

Post-merge validation: external tools/list with the service token; 302/403 without it.

Routes the cluster-apps tunnel to vmcp-gateway:4483. Safe to merge now:
the mcp CNAME and the Cloudflare Access application already exist
(tfroot-cloudflare#26 applied), so the operator only claims the managed
TXT record. Edge auth is the mcp-gateway Access app (service token for
agents, admins SSO for debug).
@xnoto
xnoto requested a review from a team as a code owner August 26, 2026 03:55
@xnoto
xnoto merged commit 2c3f114 into main Aug 26, 2026
2 checks passed
@xnoto
xnoto deleted the feat/mcp-gateway-tunnel branch August 26, 2026 03:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant