Drive a Tailscale node and its tailnet through the CLI and the control-plane API
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
TAILSCALE_API_KEYAPI keyoptionalA control-plane API access token. One of this, the OAuth client pair, or the OAuth JWT file is needed for the tailnet tools; without any of them only the local tools are offered.
TAILSCALE_OAUTH_CLIENT_SECRETOAuth appoptionalThe OAuth client secret that goes with TAILSCALE_OAUTH_CLIENT_ID.
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 2 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Drive a Tailscale node and its tailnet through the CLI and the control-plane API