Teztun
Create and manage TezTun tunnels, subdomains, and service tokens from your agent so localhost APIs and webhooks are reachable without leaving the chat.
Overview
TezTun MCP is an MCP server for the Build phase that lets agents manage TezTun tunnels, subdomains, and service tokens for exposing local services securely.
What is this MCP server?
- Manage TezTun tunnels and subdomains from MCP-compatible AI clients
- Mint and rotate service tokens (tzt_*) via documented TezTun app workflow
- stdio npm package @asadullokhn/teztun-mcp v1.0.1 with TEZTUN_TOKEN env
- Supports agent-driven setup for webhook testing and shared preview URLs
- Package version 1.0.1 as @asadullokhn/teztun-mcp on npm
- Required secret env TEZTUN_TOKEN (tzt_ prefix per schema)
What problem does it solve?
Webhook and OAuth integration work stalls because your agent cannot open a public URL to your laptop without you manually running tunnel commands.
Who is it for?
Builders on TezTun who want agent-managed tunnels while wiring payments, auth callbacks, or mobile clients to localhost.
Skip if: Teams that do not use TezTun or who need full production hosting and CI deploy pipelines instead of dev exposure.
What do I get? / Deliverables
Your agent can create and manage TezTun endpoints and tokens so partners and devices reach your dev stack through consistent subdomains.
- Agent-managed tunnel and subdomain configuration on TezTun
- Documented token usage for API calls from the agent
- Reachable HTTPS endpoints pointing at local dev services
Recommended MCP Servers
Journey fit
Tunneling is most urgent while integrating webhooks, OAuth callbacks, and mobile clients against a machine that is not on the public internet. Integrations is the right shelf because the server wires external services to your dev environment through controlled public endpoints and tokens.
How it compares
TezTun-specific tunnel MCP, not a generic multi-cloud IaC skill or ngrok-only documentation page.
Common Questions / FAQ
Who is TezTun MCP for?
Solo developers using TezTun who run MCP-enabled agents and want tunnels and tokens managed from the same workspace as their code.
When should I use TezTun MCP?
Use it when you need HTTPS callbacks to localhost, shareable preview hosts, or token rotation while building integrations.
How do I add TezTun MCP to my agent?
Mint a tzt_ service token at app.teztun.uz/tokens, set TEZTUN_TOKEN in your environment, add @asadullokhn/teztun-mcp as a stdio MCP server, and restart the client.