Schema | Tailscale Compute MCP

Tailscale Compute MCP

Describes the environment variables required to run the server.

Name	Required	Description	Default
`TAILSCALE_COMPUTE_HOST`	Yes	SSH user and direct Tailscale IP address or full MagicDNS name.
`TAILSCALE_COMPUTE_LOCAL_ROOT`	No	Absolute local project path. Defaults to MCP process directory.	MCP process directory
`TAILSCALE_COMPUTE_REMOTE_ROOT`	No	Managed remote workspace root.	.cache/tailscale-compute-mcp
`TAILSCALE_COMPUTE_REMOTE_SHELL`	No	Remote shell: auto, /bin/sh, /bin/bash, or /bin/zsh.	auto
`TAILSCALE_COMPUTE_CONNECT_TIMEOUT_SECONDS`	No	SSH connection timeout from 1 through 60 seconds.	10

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
compute_statusA	Check the configured Tailscale compute node and report its operating system, hardware, remote shell, and accelerator inventory. Use this before the first remote run or after a connection failure.
compute_runA	Sync the local project and run one non-interactive command on the configured Tailscale compute node. Use it for builds, tests, benchmarks, and other costly work. Keep file edits local. The command has the full permissions of the remote SSH user.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dylantirandaz/tailscale-compute-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server