# zrok MCP for AI Agents AI Agent Connect

> zrok lets you share local resources like web apps or databases with the public internet securely. Instead of dealing with complex firewall rules or port forwarding, you can use your AI agent to create, manage, and monitor tunnels instantly. It handles the heavy lifting of networking so you can focus on building and testing your applications in any environment.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/undefined/ai-agent-connect
- **Tags:** tunneling, reverse-proxy, open-source, network-security, remote-access

## Description

Imagine you're trying to show a client a web app running on your laptop, or you need to point a webhook to a local service for testing. Usually, this means digging through router settings, trying to find the right port to forward, and then realizing your ISP blocks it anyway. With this Connector, that whole headache disappears. You can just tell your AI agent to spin up a secure tunnel, and it handles the connection for you. It's like having a network administrator who lives inside your coding environment. You can toggle environments on and off, check how many shares you have left, or tear down tunnels once you're done. It makes your local machine reachable from anywhere without exposing your entire network. Getting this into your workflow is easy because Vinkius handles the connection, letting you jump straight into the actual work of developing and deploying. It's built for people who need to move fast and don't want to get bogged down by networking hurdles.

## Tools

### get_account
Check your current account status, remaining limits, and data usage. Monitor your capacity in real time.

### create_share
Generate a new public or private share for your local HTTP, TCP, or UDP services. This is the primary sharing tool.

### delete_share
Remove a share from the network when you no longer need the public access. Use this to secure your machine.

### register_account
Create a new zrok account directly through your AI client. You don't have to leave your workspace to sign up.

### disable_environment
Turn off an environment to stop machines from registering with the controller. This helps keep your network clean.

### enable_environment
Activate an environment so your local machines can connect to the network. Use this to start sharing.

### get_share
Fetch the specific details and connection info for a single active share. It's great for verifying links.

### list_environments
See a full list of all environments currently enabled on your account. Use this to stay organized.

### list_shares
View every active share you have running across all environments. This gives you a full network overview.

### login_account
Authenticate your credentials to receive a session token for the Connector. This connects your account to the agent.

## Prompt Examples

**Prompt:** 
```
I need to show my local website to a client. Can you make it public for me?
```

**Response:** 
```
I've created a public share for your local service. You can share this link with your client: **https://xyz-demo.share.zrok.io**

Here are the share details:
- **Type**: Public
- **Protocol**: HTTP
- **Status**: Active
- **Token**: sh_98765
```

**Prompt:** 
```
Check if I have any active tunnels running right now.
```

**Response:** 
```
I've checked your active shares. You currently have 2 active tunnels:

| Share Type | URL | Token |
| :--- | :--- | :---|
| Public | https://abc.share.zrok.io | sh_123 |
| Private | https://def.share.zrok.io | sh_456 |

Would you like me to delete either of these?
```

**Prompt:** 
```
Can you see how much of my account limit I've used?
```

**Response:** 
```
I've retrieved your account details. Here is your current usage:

- **Environments**: 3 / 10 used
- **Shares**: 5 / 20 used
- **Data Transfer**: 15% of your monthly limit

Your account is currently in good standing.
```

## Capabilities

### Create public or private shares
Open up local ports to the internet with a single command.

### Toggle environment registration
Enable or disable which machines can connect to the network.

### List all active tunnels
See every share you have running across all environments.

### View account usage limits
Check your current status and remaining data capacity.

### Delete old shares
Remove shares from the network when you no longer need them.

### Retrieve share details
Get specific connection info for any active share.

### Register new accounts
Create a new account directly through your AI client.

## Use Cases

### Webhook Testing
A developer needs to test a Stripe payment. They ask the agent to create a share for port 8000 to receive webhooks locally.

### QA Feedback
A frontend dev wants a teammate to see a local build. They ask the agent to make a public share of their local web app.

### Remote Debugging
A DevOps engineer needs to access a container on a remote machine. They use the agent to create a private share for a specific TCP port.

### Rapid Prototyping
A team is building a tool and needs to show a live demo from a laptop. They use the agent to spin up a quick public proxy.

## Benefits

- Skip the firewall headache: Use create_share to open up local ports to the internet without touching your router or complex networking rules.
- Manage resources at scale: Use list_shares and get_share to see exactly what's running across multiple machines and environments.
- Control environment access: Use enable_environment and disable_environment to manage which machines are allowed to connect to the network.
- Monitor your usage: Keep track of your limits and data consumption using get_account so you never run out of capacity unexpectedly.
- Automate tunnel cleanup: Use delete_share once your work is done to instantly shut down access to local services and keep your machine secure.

## How It Works

The bottom line is you get a way to make local services public without touching your router or firewall.

1. Connect your zrok account token to the Connector.
2. Tell your AI agent to create a share for a specific port or protocol.
3. Get a public or private URL to access your local resource instantly.

## Frequently Asked Questions

**What does the zrok MCP actually do for my development workflow?**
It lets your AI agent create secure tunnels to your local machine. You can make local apps public or create private connections for testing without changing any router settings.

**How do I use zrok MCP to test webhooks on my local machine?**
Just ask your AI agent to create a public share for the port your webhook is listening on. It will give you a public URL that you can paste into your webhook provider.

**Can the zrok MCP make my local dev site accessible to anyone?**
Yes, by creating a public share, your local site becomes accessible via a zrok URL. You can also create private shares if you only want specific people to have access.

**Is it safe to use zrok MCP for private internal resources?**
Yes, it is designed for security. You can use private sharing modes to ensure that only authorized users can reach your internal resources through the tunnel.

**How do I manage multiple tunnels using the zrok MCP?**
You can ask your agent to list all active shares or get details for a specific one. This makes it easy to keep track of multiple connections across different projects.

**Can I use the zrok MCP to see my account usage limits?**
Yes, the Connector can check your account status and show you how many environments and shares you have left, plus your current data transfer percentage.

**How do I create a public tunnel for my local web server?**
Use the `create_share` tool. Specify the `backend` (e.g., http://localhost:8080), set `share_mode` to 'public', and `backend_mode` to 'proxy'. The agent will return the public URL.

**Can I see all my currently active tunnels across all environments?**
Yes! Run the `list_shares` tool. It will retrieve a list of all active shares associated with your account, including their tokens and backend configurations.

**How do I stop an environment from being active in zrok?**
You can use the `disable_environment` tool. This will remove the environment registration from the zrok controller, effectively disconnecting that machine or container.