About teztun
teztun is an MCP server for managing TezTun tunnels, subdomains, and service tokens from compatible AI clients. Its npm package launches the official server through an installed TezTun CLI or Docker.
Key features
- 01View account and active tunnel URLs
- 02List and manage reserved subdomains
- 03List, create, and revoke service tokens
- 04View custom domains
Use cases
- 01Check the public URLs of active tunnels
- 02Reserve or release a subdomain
- 03Create or revoke a service token
- 04Review account details and custom domains
MCP support
Exposes TezTun account and infrastructure management tools to MCP clients. The npm package launches the server through the TezTun CLI or Docker.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @asadullokhn/teztun-mcpTEZTUN_TOKENSecretA TezTun service token (starts with tzt_). Mint one at https://app.teztun.uz/tokens.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project README@asadullokhn/teztun-mcp
Official TezTun MCP server, as a single-install npm package for Claude Desktop / Claude Code / Cursor / Zed / Windsurf / any Model Context Protocol client.
Lets your AI editor manage your TezTun infrastructure through chat:
- "What's my current webhook URL?" →
list_tunnels - "Reserve a subdomain called demo" →
reserve_subdomain - "Mint a service token for prod-docker, never expires" →
create_service_token - "Revoke the staging-ci token" →
revoke_service_token
Install & configure
You don't install this manually — MCP clients run it via npx. Pick your client:
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"teztun": {
"command": "npx",
"args": ["-y", "@asadullokhn/teztun-mcp"],
"env": { "TEZTUN_TOKEN": "tzt_your-token-here" }
}
}
}
Claude Code
claude mcp add --scope user teztun \
-e TEZTUN_TOKEN=tzt_your-token-here \
-- npx -y @asadullokhn/teztun-mcp
Cursor / Zed / Windsurf
Each editor has an MCP config file (~/.cursor/mcp.json, etc.). The block shape is the same as the Claude Desktop example above.
Get a service token
Sign up at app.teztun.uz, then mint a service token. On the Max plan ($10/year) tokens never expire — recommended for AI editor use.
How the package works
This package is a thin launcher. It tries, in order:
- If the TezTun CLI (
teztun) is installed, it runsteztun mcp. - If Docker is available, it runs
docker run --rm -i -e TEZTUN_TOKEN asadullokhn/teztun:latest mcp. - Otherwise it errors with install instructions.
No bundled binaries, no postinstall side effects. The MCP server itself is the Go binary from teztun.uz/download, or the asadullokhn/teztun image on Docker Hub.
Exposed tools
| Tool | What it does |
|---|---|
get_account | Current user (plan, status) |
list_tunnels | Active tunnels with their public URLs |
list_subdomains | Reserved subdomains |
reserve_subdomain(name) | Reserve a new subdomain (plan-gated) |
release_subdomain(id) | Release a reserved subdomain (destructive) |
list_custom_domains | Custom domains on the Max plan |
list_service_tokens | Service tokens the user has minted |
create_service_token(name, expiry_seconds?, expire_never?) | Mint a token |
revoke_service_token(id) | Revoke a service token (destructive) |
Links
- Product: https://teztun.uz
- Dashboard: https://app.teztun.uz
- Docs: https://teztun.uz/docs/mcp-server
- API reference: https://teztun.uz/docs/api
- Docker image: asadullokhn/teztun
- Support: [email protected]
License
MIT. Launcher only — the MCP server binary it spawns is the official TezTun client.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.