Skip to content
Vinkius

zrok (Open-Source Tunnel) Connector for AI agents.

10 live capabilities

Securely expose local dev sites and webhooks to the public internet.

Live agent request zrok (Open-Source Tunnel) / Connector

Waiting for input…

AI Agent

Why people use zrok (Open-Source Tunnel)

Zrok for Securely Exposing Local Dev Environments

With the zrok MCP, you just tell your AI agent to make the local app public. It handles the tunnel creation in seconds and gives you a URL you can send over Slack. You get back to coding instead of fighting with your network hardware.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • Visual Studio Code
  • Windsurf

What Vinkius changes

You get a way to make local services public without touching your router or firewall.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 5,900+ Connectors

  1. Real-world use case 01

    Webhook Testing

    A developer needs to test a Stripe payment.

  2. Real-world use case 02

    QA Feedback

    A frontend dev wants a teammate to see a local build.

  3. Real-world use case 03

    Remote Debugging

    A DevOps engineer needs to access a container on a remote machine.

Complete set · 10capabilities

The complete zrok (Open-Source Tunnel) capability set.

These are the exact actions your AI can choose when you ask it to work with zrok (Open-Source Tunnel).

Capability set01 / 03

01—04

4 capabilities in this set.

Part of 10 available through zrok (Open-Source Tunnel).

  1. 01 Capability

    Get account

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

  2. 02 Capability

    Create share

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

  3. 03 Capability

    Delete share

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

  4. 04 Capability

    Register account

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

Capability set02 / 03

05—07

3 capabilities in this set.

Part of 10 available through zrok (Open-Source Tunnel).

  1. 05 Capability

    Disable environment

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

  2. 06 Capability

    Enable environment

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

  3. 07 Capability

    Get share

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

Capability set03 / 03

08—10

3 capabilities in this set.

Part of 10 available through zrok (Open-Source Tunnel).

  1. 08 Capability

    List environments

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

  2. 09 Capability

    List shares

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

  3. 10 Capability

    Login account

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

Set up in minutes

One URL. Then ask zrok (Open-Source Tunnel) to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use zrok (Open-Source Tunnel) from the conversation.

Choose your client

Live preview
Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP
https://edge.vinkius.com/vk_preview_ClXF7DisyXQ0EoLqQIltNLLkA1JbCPYyg6iY16El/mcp
  1. Step 01

    Open Connectors

    In Claude Web or Claude Desktop, open Settings and choose Connectors.

  2. Step 02

    Add the URL

    Choose Add custom connector, name it zrok (Open-Source Tunnel), and paste the URL above.

  3. Step 03

    Turn it on in chat

    Select +, open Connectors, and enable zrok (Open-Source Tunnel) for the conversation.

Where the request belongs

Work zrok can move forward.

Built around the request

For the developer who needs to share a local build with a teammate or the DevOps pro managing remote environments across multiple machines.

01

Frontend Developer

Exposing a local React app to a remote QA tester for a quick feedback loop.

02

Backend Engineer

Pointing a Stripe webhook to a local environment without a public IP.

03

Security Researcher

Creating a private share to test a vulnerability in a sandboxed container.

Bring your own AI

Change the model, client or framework. Keep zrok connected.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • VS Code
  • Windsurf
  • ZCode
  • Cline
  • Zed
  • Continue
  • Kiro
  • Roo Code
  • Zencoder
  • Goose
  • Void
  • Augment Code
  • Amp
  • Qodo
  • Tabnine
  • Pieces
  • Sourcegraph Cody
  • JetBrains
  • Warp
  • Amazon Q
  • Antigravity
  • BoltAI
  • Raycast
  • Jan
  • LM Studio
  • AnythingLLM
  • Open WebUI
  • Msty
  • Cherry Studio
  • LibreChat
  • TypingMind
  • Chorus
  • 5ire
  • n8n
  • LangChain
  • LlamaIndex
  • CrewAI
  • Vercel AI SDK

Before you connect

Questions about zrok.

The practical details behind the request, access and result.

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 capability. 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 capability. 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 capability. This will remove the environment registration from the zrok controller, effectively disconnecting that machine or container.

One connection away

Give your agent a direct line to zrok.

Connect zrok once. Keep it beside 5,900+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available