Cursor plugin specification and official plugins
TypeScript
tailscale: one-click personal Connect, several company tailnets, Premium posture note and no client on the bot computer in the setup skill (1.0.3)
Eric G.Y Liu0b20c5ed7c1f
diff --git a/third_party/tailscale/.cursor-plugin/plugin.json b/third_party/tailscale/.cursor-plugin/plugin.jsonindex 4572d4d6..396ee234 100644--- a/third_party/tailscale/.cursor-plugin/plugin.json+++ b/third_party/tailscale/.cursor-plugin/plugin.json@@ -1,13 +1,13 @@{"name": "tailscale","displayName": "Tailscale",- "version": "1.0.2",+ "version": "1.0.3","minClientVersions": {"cursor": "never","grokbot": "0.49.0","sand": "0.49.0"},- "description": "Let Grok Bot reach MCP servers on your private Tailscale network. On your own tailnet it joins as one tag:grokbot device; on your team's company tailnet, turned on by a team admin, it uses each member's own device.",+ "description": "Let Grok Bot reach MCP servers on your private Tailscale network: connect your own tailnet, or your team's company tailnets turned on by a team admin, with each member using their own device.","author": {"name": "Cursor","email": "[email protected]"diff --git a/third_party/tailscale/skills/tailscale-setup/SKILL.md b/third_party/tailscale/skills/tailscale-setup/SKILL.mdindex 6f80344d..3b111e65 100644--- a/third_party/tailscale/skills/tailscale-setup/SKILL.md+++ b/third_party/tailscale/skills/tailscale-setup/SKILL.md@@ -1,6 +1,6 @@---name: tailscale-setup-description: Walk a user or team admin through connecting Grok Bot to a Tailscale tailnet - a personal tailnet with one tag:grokbot device, or a team's company tailnet with each member's own device - granting only the MCP hosts it should reach, and adding tailnet MCP servers, including ones on internal DNS names, behind subnet routes or app connectors, on any port, or with a private CA. Use when the user asks to set up, troubleshoot, or disconnect Grok Bot's Tailscale connection.+description: Walk a user or team admin through connecting Grok Bot to a Tailscale tailnet - a personal tailnet (one-click Connect, or a tag:grokbot device when the user's policy should limit it), or a team's company tailnets with each member's own device - granting only the MCP hosts it should reach, and adding tailnet MCP servers, including ones on internal DNS names, behind subnet routes or app connectors, on any port, or with a private CA. Use when the user asks to set up, troubleshoot, or disconnect Grok Bot's Tailscale connection.---# Tailscale setup for Grok Bot@@ -10,14 +10,16 @@ Grok Bot reaches MCP servers on a tailnet in one of two ways. Find out which one| | Personal tailnet | Company tailnet ||---|---|---|| Who turns it on | The user | A Grok Bot team admin, once for the team |-| Device | One device for the bot, tagged `tag:grokbot` | Each member's own Grok Bot device, owned by that member and carrying the `custom:grokbot` attribute |-| Policy | Grants to `tag:grokbot` | The member's usual access, narrowed with a posture on `custom:grokbot` |-| Plugin row | **Tailscale** | **Tailscale (team)** |+| Device | The user's own Grok Bot device (one-click Connect), or one device tagged `tag:grokbot` | Each member's own Grok Bot device, owned by that member and carrying the `custom:grokbot` attribute on Premium or Enterprise plans |+| Policy | The user's own access, or grants to `tag:grokbot` when using the tag | The member's usual access, narrowed with a posture on `custom:grokbot` |+| Plugin row | **Personal tailnet** | **Company tailnet for \<team\>** |If signing in on the personal row fails with a `tag:grokbot` error on a company tailnet, use the company tailnet.## Personal tailnet+If the row offers **Connect**, click it, approve on Tailscale's screen, then confirm the Tailscale login the row shows. Only an owner or admin of that tailnet can connect it this way, and the device gets the user's own access. To limit Grok Bot with the user's own grants instead, use **Connect with tag:grokbot** and the steps below. If the row offers **Authenticate**, use the steps below.+1. In the Tailscale admin console, open **Access controls** and merge these keys into the policy file instead of replacing it:```hujson@@ -43,10 +45,9 @@ If signing in on the personal row fails with a `tag:grokbot` error on a companyThe team admin does this once:-1. During the beta, Tailscale enables Grok Bot device provisioning one tailnet at a time. Send Grok Bot support the tailnet ID (Tailscale admin console, **Settings → General**). Until it's enabled, members' sign-ins fail.-2. Add the Tailscale plugin to the team.-3. On cursor.com, open **Integrations → Tailscale** (or, in Grok Bot, the **Company tailnet** card on the **Tailscale** plugin). Enter the tailnet's MagicDNS suffix (like `tail1234.ts.net`) or click **Sign in to Tailscale** to fill it in, check **Members' Grok Bot devices may join this tailnet**, and click **Enable**.-4. Lock Grok Bot devices down in the policy file. A member's Grok Bot device belongs to that member, so without this it gets everything the member can reach. Default postures are OR'd, so add `custom:grokbot NOT SET` to each one (or add one default posture with just that condition if the policy has none), then grant MCP hosts with a posture that requires the attribute:+1. Add the Tailscale plugin to the team.+2. In Grok Bot, open the **Tailscale** plugin's **Company tailnet** card. On the new cursor.com dashboard, the same setting is the **Tailscale** card under **Integrations** that says "Let your team's Grok Bot reach MCP servers on your company's Tailscale network"; the Tailscale page that asks for an OAuth client and a tag is for Rollouts, not Grok Bot. Enter the tailnet's MagicDNS suffix (like `tail1234.ts.net`) or click **Sign in to Tailscale** to fill it in, check **Members' Grok Bot devices may join this tailnet**, and click **Enable**. If the team's members are spread across more than one tailnet (for example two companies in one team), list each tailnet; a member's device is kept on any listed tailnet.+3. Lock Grok Bot devices down in the policy file. A member's Grok Bot device belongs to that member, so without this it gets everything the member can reach. The `custom:grokbot` attribute needs Tailscale Premium or Enterprise; on other plans Grok Bot devices can't be told apart from the member's other devices. Default postures are OR'd, so add `custom:grokbot NOT SET` to each one (or add one default posture with just that condition if the policy has none), then grant MCP hosts with a posture that requires the attribute:```hujson{@@ -68,7 +69,11 @@ The team admin does this once:Use the groups that already reach each MCP host, so people get the same access from Grok Bot that they have today, and nobody has to request anything new.-Each member then opens the **Tailscale** plugin and clicks **Connect** on the row that names the team and tailnet. On Tailscale's screen, the tailnet shown at the top right must be the company tailnet; then click **Authorize application**. Their device joins the company tailnet as them. With device approval on, a tailnet admin approves the `grokbot-team-…` device on the **Machines** page; Tailscale doesn't notify them.+Each member then opens the **Tailscale** plugin and clicks **Connect** on the row that names the team and tailnet. They sign in with the account that's in a company tailnet (if that account belongs to more than one tailnet, they pick it on Tailscale's screen), then click **Authorize application**. Their device joins the company tailnet as them. With device approval on, a tailnet admin approves the `grokbot-team-…` device on the **Machines** page; Tailscale doesn't notify them.++## Don't install Tailscale on the bot's computer++Grok Bot reaches tailnet MCP servers through this plugin. Don't install the Tailscale client on the bot's computer: it's wiped whenever the computer is replaced and keeps asking to log in again.## Add MCP servers@@ -100,7 +105,7 @@ The bundle has to be the real certificate text. A placeholder or a file path won## Disconnect-Click **Remove** on the Tailscale plugin page. A team admin can turn the company tailnet off with **Disable**.+Click **Remove** on the Tailscale plugin page. A team admin can turn the company tailnet off with **Disable**. Grok Bot devices follow the tailnet's key expiry; when a key expires, reconnect, or disable key expiry on the device.## Troubleshooting@@ -109,6 +114,7 @@ Click **Remove** on the Tailscale plugin page. A team admin can turn the company- **Name doesn't resolve:** the tailnet's DNS has to resolve it. Check MagicDNS and the split DNS settings on the **DNS** page.- **`destination_not_routed`:** the address isn't on a subnet route or app connector the device can use.- **Certificate error:** the server uses a private CA. Add `tls.caBundle` with the CA's PEM.-- **"Your tailnet hasn't allowed Grok Bot's Tailscale app":** Tailscale hasn't enabled the beta for that tailnet yet; send support the tailnet ID.-- **"Signed in to a different tailnet":** Tailscale hasn't enabled the beta for the company tailnet yet and the member's account is also in another tailnet, so the device joined that one and Grok Bot signed it out. Confirm with support that the tailnet is enabled, then click **Connect** again and check the tailnet at the top right of Tailscale's screen.+- **"Your tailnet hasn't allowed Grok Bot's Tailscale app":** ask the tailnet's admin to allow it, then connect again.+- **Signed out because the device joined another tailnet:** the member's account landed in a tailnet the team doesn't list. Connect again with the account that's in a listed tailnet, or ask the team admin to add that tailnet.+- **"Only an owner or admin of this tailnet can connect it":** the user is a regular member of that tailnet. Ask its admin to set it up as the team's company tailnet, or connect a tailnet the user runs.- **Sign-in can't apply the tag:** the signing-in user isn't an owner of `tag:grokbot` in `tagOwners`.