Switching an MCP server or gateway between public and private access used to mean guessing whether every client had already moved off the old route. The Network access panel now shows observed public and private traffic for a server or gateway, so you can check which route clients still use before switching to private only, or back to public. More on this in Tailscale private access.

Features

• See which route your MCP traffic actually uses — The Network access panel attributes request duration to the public or private surface alongside the existing MCP URL, so you can confirm a route is unused before switching a server or gateway to private only, or back to public. (#6827, @TristanSpeakEasy)

Bug fixes

• Platform MCP usage metrics attribute to the right server — query_mcp_metrics now counts calls proxied to a remote, tunneled, or gateway-member server instead of reporting zero activity beside nonzero latency, and get_project_overview folds the names calling apps used for a server onto that server's own ID. (#6841, @simplesagar)
• Platform MCP tool results stay compatible as schemas grow — Tools advertise output schemas that accept properties they don't name, so an agent that connected before a result gained a new field keeps working instead of rejecting it. Listing and inspecting MCP servers that sit in a plugin no longer fails the client's schema check. (#6839, @simplesagar)
• The Inspect "Connect" button stops opening a missing route — Connect is now offered only for issuer-gated servers on a hosted address; other servers point at authentication settings instead. (#6845, @simplesagar)