Reaching private MCP servers and internal tools
The official account @bot of the AI agent "Grok Bot" announced on X on Nov. 10 (7:16:43 a.m. Nov. 11 Japan time) that Grok Bot can now join personal or company Tailscale networks, known as "tailnets." It said the feature is meant for securely reaching private MCP servers, internal tools and apps on a user's network. MCP (Model Context Protocol) is a way of connecting AI to external tools and data, and an MCP server acts as the entry point.
Grok Bot can now join your personal or company tailnets on Tailscale. Use it to securely reach private MCP servers, internal tools, and apps on your network.
Joining a tailnet as a device tied to the user's identity
Tailscale introduced its integration with Grok Bot in an official blog post dated Nov. 9. The post calls a tailnet a user's "Tailscale network" and says internal infrastructure should not have to be exposed to the public internet just so an AI agent can use it.
The integration uses "Tailscale OAuth apps," which the blog says are now generally available. The mechanism connects a tailnet to AI agents through a standard OAuth 2.0 authorization flow. Tailscale's existing "OAuth clients" create devices under a shared service identity, while OAuth apps act on behalf of the user who authorizes them. Devices added this way carry the user's identity, so tailnet access policies, audit logs and device quotas apply to them just as they do to other devices, the company said.
According to the blog, this flow is already in production, and Grok Bot can use OAuth apps to connect to private MCP servers on a tailnet without exposing them to the public internet. Users stay in control of what it can access and do not have to paste keys or secrets anywhere, the blog said. When Grok Bot is connected to Tailscale, it joins the tailnet as a device associated with the user's identity and, like other devices, follows the tailnet's policy controls.
Tailscale's rules limit what it can reach
The blog describes a setup in which Grok Bot can reach an internal MCP server but not everything else the user's laptop can reach. Grok Bot added to a tailnet on Tailscale's Premium or Enterprise plan gets a custom "posture" (device state) attribute, so its access can be set by policy separately from the user's other devices. On other plans, similar control is possible by assigning a tag to Grok Bot's device after authentication and using tag-based rules, the blog said.
As an example policy, the blog showed engineers reaching production databases from their regular devices, while Grok Bots tied to those engineers can reach only designated MCP servers. A default rule keeps existing access rules from applying to Grok Bot devices, and only the rule for MCP servers is allowed as an exception. This lets Grok Bot reach MCP servers without inheriting the user's broader network access, the blog said.
Availability: Grok Bot plans are not stated
According to Tailscale's blog, users connect through the Tailscale plugin in the Grok Bot desktop app. On Tailscale's side, custom posture attributes are available on the Premium and Enterprise plans. Neither @bot's post nor Tailscale's blog states which Grok Bot plans can use the feature, which regions are covered, what it costs or when it becomes available.
SpaceXSI's official documentation page "Connect to private networks" (updated Oct. 29) describes a separate method in which administrators on the Enterprise plan use "Team Setup Scripts" to install networking software such as Tailscale on every team computer. The page says this method is Enterprise only and that installing, configuring and authenticating the networking software is the customer's responsibility. The same page does not mention the newly announced ability to join a tailnet.
The next day, Nov. 11 (Nov. 12 Japan time), Grok Bot also announced "Grok Bot 1.0", which adds features such as sharing the same bot across a team and joining meetings.
