infra(deploy): serve MCP on multiple domains + SKIP_BUILD #4
Loading…
Reference in a new issue
No description provided.
Delete branch "infra/deploy-multidomain"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR carries two changes for the read-only Analytics MCP, both reflecting what is already running in prod on twala:
1. Multi-domain routing (
fae4094) — serve the MCP on bothfleetmcp.rahamafresh.comandfleetmcp.fivetitude.comfrom one Traefik router/cert, plusSKIP_BUILD=1for label/env-only redeploys. The live container already answers on both domains;maindid not, so a redeploy frommainwould drop the second domain.2. Caller attribution in query logs (
af6fdbc) — BearerAuth matched a per-analyst token but only stashed it onrequest.state, which FastMCP tools never see, soquery()logged with no caller. Bridge it through a ContextVar and logcaller=<name>per query, so the per-token attribution the auth design promises actually shows up in the logs.Note: merging only aligns source with prod; the running container still needs a manual
deploy.sh(orSKIP_BUILD=0rebuild) to pick up the logging change.🤖 Generated with Claude Code