@yawlabs/tailscale-mcp 0.6.4 → 0.6.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +16 -1
- package/dist/index.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -34,6 +34,8 @@ export TAILSCALE_API_KEY="tskey-api-..."
|
|
|
34
34
|
|
|
35
35
|
**2. Create `.mcp.json` in your project root**
|
|
36
36
|
|
|
37
|
+
macOS / Linux / WSL:
|
|
38
|
+
|
|
37
39
|
```json
|
|
38
40
|
{
|
|
39
41
|
"mcpServers": {
|
|
@@ -45,7 +47,20 @@ export TAILSCALE_API_KEY="tskey-api-..."
|
|
|
45
47
|
}
|
|
46
48
|
```
|
|
47
49
|
|
|
48
|
-
|
|
50
|
+
Windows:
|
|
51
|
+
|
|
52
|
+
```json
|
|
53
|
+
{
|
|
54
|
+
"mcpServers": {
|
|
55
|
+
"tailscale": {
|
|
56
|
+
"command": "cmd",
|
|
57
|
+
"args": ["/c", "npx", "-y", "@yawlabs/tailscale-mcp"]
|
|
58
|
+
}
|
|
59
|
+
}
|
|
60
|
+
}
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
> **Why the extra step on Windows?** Since Node 20, `child_process.spawn` cannot directly execute `.cmd` files (that's what `npx` is on Windows). Wrapping with `cmd /c` is the standard workaround and is what MCP clients expect. This file is safe to commit — it contains no secrets.
|
|
49
64
|
|
|
50
65
|
**3. Restart and approve**
|
|
51
66
|
|
package/dist/index.js
CHANGED
|
@@ -23351,7 +23351,7 @@ var workloadIdentityTools = [
|
|
|
23351
23351
|
];
|
|
23352
23352
|
|
|
23353
23353
|
// src/index.ts
|
|
23354
|
-
var version2 = true ? "0.6.
|
|
23354
|
+
var version2 = true ? "0.6.5" : (await null).createRequire(import.meta.url)("../package.json").version;
|
|
23355
23355
|
var subcommand = process.argv[2];
|
|
23356
23356
|
if (subcommand === "deploy-acl") {
|
|
23357
23357
|
const filePath = process.argv[3];
|