zrok (Open-Source Tunnel) MCP. Expose local ports, manage tunnels via chat.

zrok lets your AI agent expose local resources to the world. You don't have to deal with firewalls or manually running networking commands anymore; your agent handles all the messy stuff in a simple conversation.

To get started, you first need access. Your agent can run register_account if it’s brand new to zrok, setting up your account and grabbing your initial authorization tokens. If you're already set up, running login_account authenticates the connection by exchanging credentials for an active zrok access token. After that, you've got the keys to the kingdom.

Sharing Local Resources

You can expose any local port—HTTP, TCP, or UDP—by using create_share. You just tell your agent what service needs a tunnel and whether it should be public or private. The agent handles building that secure network path for you. For instance, if you run create_share for a web server on port 8080, the AI client instantly routes that service to a usable URL without you touching a single firewall rule.

Need to check what’s running? You can use list_shares, which gives you a full rundown of every active tunnel and its associated details. If you want specific info on one share—say, the status or destination of an existing tunnel—you run get_share and tell it exactly which resource you're checking.

When you're done with a service, don’t leave tunnels hanging. You shut them down immediately by calling delete_share, which removes the active share and kills the network connection associated with that tunnel. It’s clean, quick work.

Managing Environments

The server lets you manage multiple development environments so you can keep your resources organized. If you need to make sure no one accidentally uses an old setup, you run disable_environment on a specific environment name; this takes that entire environment offline and stops any new resources from being shared through it.

To bring a workspace back online, you use enable_environment. This reactivates the whole zone, letting machines or containers register and share their resources again. You can see all the available workspaces by listing them with list_environments.

Monitoring and Account Status

You keep tabs on everything your agent is doing. Running list_shares shows you every single active tunnel running right now, letting you know exactly what's exposed to the outside world. For a comprehensive status check—checking usage counts against defined limits or seeing how much bandwidth you’ve used—you run get_account. This gives you your current account health report.

If you need to manage which environments are even available for sharing, you can use list_environments to pull up the names of all currently registered development areas. Everything is contained in these simple commands: setting up accounts via register_account, authenticating with login_account, creating tunnels with create_share, monitoring everything with get_share and list_shares, controlling the scope with environment tools, and cleaning up with delete_share.

It’s that direct. No fluff, no manual CLI commands.