Developer · Local MCP server
Tailscale Compute
Run builds, tests, and benchmarks on your own Tailscale compute node.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.dylantirandaz/tailscale-compute- Version
- 0.1.0-beta.3
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-08-13
- Updated
- 2026-08-13
- Publisher
- dylantirandaz (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/dylantirandaz) · how
- Repository
- github.com/dylantirandaz/tailscale-compute-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @dylantirandaz/tailscale-compute-mcp | 0.1.0-beta.3 | stdio |
How to connect Tailscale Compute
Tailscale Compute runs locally from a Node.js package published to the npm registry: @dylantirandaz/tailscale-compute-mcp version 0.1.0-beta.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @dylantirandaz/tailscale-compute-mcp@0.1.0-beta.3. It reads these environment variables: TAILSCALE_COMPUTE_HOST (required), TAILSCALE_COMPUTE_LOCAL_ROOT, TAILSCALE_COMPUTE_REMOTE_ROOT, TAILSCALE_COMPUTE_REMOTE_SHELL, TAILSCALE_COMPUTE_CONNECT_TIMEOUT_SECONDS and TAILSCALE_COMPUTE_AUDIT_LOG; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"tailscale-compute": {
"command": "npx",
"args": [
"-y",
"@dylantirandaz/tailscale-compute-mcp@0.1.0-beta.3"
],
"env": {
"TAILSCALE_COMPUTE_HOST": "<value>",
"TAILSCALE_COMPUTE_LOCAL_ROOT": "<value>",
"TAILSCALE_COMPUTE_REMOTE_ROOT": "<value>",
"TAILSCALE_COMPUTE_REMOTE_SHELL": "<value>",
"TAILSCALE_COMPUTE_CONNECT_TIMEOUT_SECONDS": "<value>",
"TAILSCALE_COMPUTE_AUDIT_LOG": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| TabulaCross-AI personal memory. Save once in ChatGPT, recall in Claude, Mistral, Grok, or any MCP client. | Remote · HTTPLive check: sign-in required |
| Tada: automated QA for AI-written codeYour coding agent asks Tada to work through a feature in a real browser and gets back a verdict. | Local · stdio |
| TailscaleDrive a Tailscale node and its tailnet through the CLI and the control-plane API. | Local · stdio |
| TailscaleRead devices, users, keys, ACLs and DNS for a tailnet; manage devices, routes and auth keys. | Remote · HTTPLive check: ✓ handshake |
| Tailscale MCP ServerSecure MCP access for private infrastructure over Tailscale - 48 tools across 9 domains. | Local · stdio |
| Tailscale RMCPTailscale device, route, DNS, key, user, and ACL management over MCP and CLI. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| Tailscale RMCPRust MCP server and CLI for Tailscale devices, users, keys, policies, and auth. | Local · stdio |
| Tailwind V4 Upgrade Blocker Lint19 rules that find the Tailwind v3 syntax Tailwind v4 removed or silently redefined, in the file you. | Local · stdio |