tailnet-mcp
by zedong-peng
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| v | No | Flag -v: add tsnet's own logs to stderr. | |
| url | Yes | The URL of the Streamable HTTP MCP server inside the tailnet (flag -url), e.g. https://server.tailnet.ts.net:8443/<path>. | |
| check | No | Flag -check: connect, print the server's tools on stderr and exit. | |
| state | No | Directory where the node key is kept (flag -state). Keep it on persistent storage. | ~/.local/state/tailnet-mcp/<hostname> |
| hostname | Yes | The tailnet node hostname for this bridge process (flag -hostname). Each process is its own tailnet node, so use a different hostname per server. | |
| TS_AUTHKEY | No | One-time, pre-authorized Tailscale auth key with a tag for the agent (e.g. tskey-auth-...). Only needed for the first login; the node key is then kept in -state. |
Instructions
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.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues