Answer: The 'Failed to connect' status can be caused by several issues that must be checked in order: the OAuth client needs the `auth_keys` scope and permission to assign the connection's tag (which must be listed in `tagOwners`), the policy must allow the Cursor tag to reach the server's host on the port in its URL (or `443` when the URL has no port), posture rules applying to the Cursor tag can block Cursor's devices, Tailnet Lock requires new devices to be signed before connecting, and only an `https` URL can use a Tailscale connection. Status: Confirmed Entry: tool/cursor/troubleshooting/tailscale-failed-to-connect Revision: 1 Digest: sha256:462d468e2fc4a407 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:11:07Z Last changed: 2026-11-13T03:11:07Z Last verified: 2026-11-20T12:38:47Z Next check: 2026-11-21T12:38:47Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of OAuth scope | auth_keys | [1] | 2026-11-20 Tag owners requirement | tagOwners | [1] | 2026-11-20 Default port | 443 | [1] | 2026-11-20 Posture rule example | defaultSrcPosture | [1] | 2026-11-20 Tailnet Lock requirement | new devices must be signed before they can connect | [1] | 2026-11-20 URL scheme requirement | https | [1] | 2026-11-20 Sources: [1] Anysphere. "cursor.com/docs/integrations/tailscale.md". https://cursor.com/docs/integrations/tailscale.md Role: primary. Accessed: 2026-11-20T12:38:47Z Quote: "The OAuth client needs the `auth_keys` scope and permission to assign" (Supports: OAuth scope) Quote: "The tag must be listed in `tagOwners`." (Supports: Tag owners requirement) Quote: "port in its URL, or `443` when the URL has no port." (Supports: Default port) Quote: "`defaultSrcPosture` or a `srcPosture` on its rule, can block Cursor's" (Supports: Posture rule example) Quote: "With Tailnet Lock, new devices must be signed before they can connect." (Supports: Tailnet Lock requirement) Quote: "Only an `https` URL can use a Tailscale connection." (Supports: URL scheme requirement) Snapshot SHA-256: 05956c7df606c9be2e52dbed77bbd31c1c7a7deaf30a53316aaadf5a46ea5b6b (captured 2026-11-13T03:11:06Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:11:07Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:38:47Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:38:47Z Last attempt: 2026-11-20T12:38:47Z Notes and limitations: Extracted automatically from a single official source (section "The server shows Failed to connect"). Related: https://latestn.com/tool/cursor/troubleshooting/terminal-output-truncated-misformatted Why is Cursor terminal command output truncated or misformatted? https://latestn.com/tool/cursor/troubleshooting/terminal-unavailable-live-workspace Why is the terminal unavailable in the Cursor Self-Hosted Machines live workspace? https://latestn.com/tool/cursor/troubleshooting/test-webhooks-locally How do I test Cursor webhook agents locally? https://latestn.com/tool/cursor/troubleshooting/scim-sync-troubleshooting Why aren't my users or groups syncing with Cursor SCIM? https://latestn.com/tool/cursor/troubleshooting/sso-user-not-assigned-error How do I fix the Cursor SSO error 'User is not assigned to this application'? https://latestn.com/tool/cursor/troubleshooting/subagent-not-delegated Why isn't Cursor delegating to my subagent? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:11:07Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cursor/troubleshooting/tailscale-failed-to-connect/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cursor/troubleshooting/tailscale-failed-to-connect POST: https://latestn.com/dispute/tool/cursor/troubleshooting/tailscale-failed-to-connect with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/troubleshooting/tailscale-failed-to-connect?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). Why does Cursor show 'Failed to connect' for my Tailscale MCP server? Revision 1, last verified 2026-11-20T12:38:47Z. https://latestn.com/tool/cursor/troubleshooting/tailscale-failed-to-connect (accessed 2026-11-21T09:58:48Z). @misc{LatestN_tool_cursor_troubleshooting_tailscale_failed_to_connect_r1, title = {Why does Cursor show 'Failed to connect' for my Tailscale MCP server?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/troubleshooting/tailscale-failed-to-connect}}, note = {Revision 1; digest sha256:462d468e2fc4a407; last verified 2026-11-20T12:38:47Z; accessed 2026-11-21T09:58:48Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cursor/troubleshooting/tailscale-failed-to-connect