{ "_comment": "Tailscale Serve on koala, not the public d-ma.be hostnames. The public path exits to Cloudflare and NPM to reach a k3s service on the same machine most sessions run on, which imposes rate limits and message-size caps on tool results. Serve terminates TLS with a real Tailscale cert and proxies to the NodePort over loopback, so traffic reaches the service from koala itself and satisfies the default-deny-ingress NetworkPolicy with no cluster change. Clients need 'tailscale set --accept-dns=true' for the MagicDNS name to resolve; see mathias/skills#24.", "mcpServers": { "brain": { "type": "http", "url": "https://koala.tail30472e.ts.net:8443/mcp", "headers": { "Authorization": "Bearer ${BRAIN_MCP_TOKEN}" } }, "infra": { "type": "http", "url": "https://koala.tail30472e.ts.net:8444/mcp" } }, "_parked": { "_reason": "cad and gitea-mcp are proxied, reachable and AUTHENTICATING: tailscale serve 8445 -> 127.0.0.1:31877 and 8446 -> 127.0.0.1:30340; an MCP initialize with the correct bearer returns 200 from both (serverInfo gitea-mcp 0.1.0, cad aed2aaf). They stay parked only because nothing puts those two tokens into the session environment. Both live in the 1Password AgentSecrets vault, and by deliberate design (infra#224, closed) no single identity on koala reads both vaults: koala-homelab is HomeLab-only and resolves ~/.op-env, koala-agentsecrets-write is AgentSecrets-only and lives in ~/.op-agent-write.env. Adding an AgentSecrets reference to ~/.op-env does NOT degrade gracefully -- `op run` fails wholesale and every other token, BRAIN_MCP_TOKEN included, goes unresolved with it. Enabling needs a read-scoped AgentSecrets identity in the session-env path; see mathias/skills#32, #33.", "cad": { "type": "http", "url": "https://koala.tail30472e.ts.net:8445/mcp", "headers": { "Authorization": "Bearer ${CAD_MCP_TOKEN}" } }, "gitea": { "type": "http", "url": "https://koala.tail30472e.ts.net:8446/mcp", "headers": { "Authorization": "Bearer ${GITEA_MCP_STATIC_TOKEN}" } } } }