zrok-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@zrok-mcpShare my local server on port 3000 publicly via zrok"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
zrok-mcp
An MCP server for zrok — the open-source secure sharing platform built on OpenZiti. Lets AI agents manage zrok tunnels, shares, and access programmatically.
Supports three transports: stdio (local), streamable-http and SSE (remote/Bifrost).
Tools
Each tool uses an action parameter to select the operation — no need to remember many tool names.
zrok_env — Environment management
Action | Description |
| Check environment status (enabled, API endpoint, identity) |
| Enable the zrok environment with an account token |
| Disable the current zrok environment |
zrok_share — Share management
Action | Description |
| Create a public or private share |
| Delete a share by token |
| List all shares with optional filters |
zrok_access — Access management
Action | Description |
| Create access to a private share |
| Remove access to a share |
| List all accesses with optional filters |
Related MCP server: @beyondidentity/mcp
Requirements
Python 3.10+
zrok2 Python SDK
A zrok account and enabled environment
Install
cd zrok-mcp
pip install -e .Run
Transport is selected via the ZROK_MCP_TRANSPORT environment variable (default: stdio).
Transport | Use case |
| Local clients (Claude Desktop, Cursor, Crush) |
| Remote / Bifrost gateway (recommended) |
| Remote / Bifrost gateway (legacy SSE) |
STDIO (default)
zrok-mcpStreamable HTTP (remote)
ZROK_MCP_TRANSPORT=streamable-http ZROK_MCP_PORT=8000 zrok-mcpDocker (remote)
docker build -t zrok-mcp .
docker run -p 8000:8000 -v ~/.zrok2:/root/.zrok2 zrok-mcpWith MCP Inspector
mcp dev src/zrok_mcp/server.pyEnvironment Variables
Variable | Default | Description |
|
| Transport: |
|
| Bind host (HTTP/SSE transports) |
|
| Bind port (HTTP/SSE transports) |
Configuration
Claude Desktop (stdio)
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"zrok": {
"command": "uv",
"args": ["--directory", "/path/to/zrok-mcp", "run", "zrok-mcp"]
}
}
}Cursor / Crush (stdio)
Add to your crush settings or MCP config:
{
"zrok": {
"command": "uv",
"args": ["--directory", "/path/to/zrok-mcp", "run", "zrok-mcp"]
}
}Bifrost AI Gateway (streamable-http)
Deploy zrok-mcp as a remote HTTP server (Docker, Railway, etc.)
In the Bifrost Web UI, go to MCP Gateway → New MCP Server
Select HTTP as the connection type
Enter the URL:
http://your-zrok-mcp-host:8000/mcpSet
tools_to_executeto["*"](or filter as needed)
Or via config file:
{
"mcp": {
"mcp_clients": [
{
"name": "zrok",
"connection_type": "http",
"connection_string": "http://your-zrok-mcp-host:8000/mcp",
"tools_to_execute": ["*"]
}
]
}
}For SSE transport, use connection_type: "sse" and connection_string: "http://your-zrok-mcp-host:8000/sse".
Example Usage
Once configured, your AI agent can do things like:
"Share my local server on port 3000 publicly via zrok"
The agent will call zrok_share(action="create", target="http://localhost:3000") and return the public URL.
"List all my zrok shares"
The agent will call zrok_share(action="list") and show token, mode, target, and endpoints.
"Create a private TCP tunnel for my database on port 5432"
The agent will call zrok_share(action="create", share_mode="private", backend_mode="tcpTunnel", target="localhost:5432").
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Manage ngrok from your agent: endpoints, domains, and traffic policy.
Provides capabilities that let LLM agents perform a range of infrastructure management tasks.
Manage SRG+ hubs, channels, content, assets, users, and workspaces from any MCP-aware AI agent.
Context and control for any AI. Agent identity, scoped access, and proof across tools.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage agents, webhooks, and P2P connectivity on the Anycast network, allowing operations like listing agents, creating tokens, and viewing connection stats.4 npmMIT
- AlicenseBqualityCmaintenanceEnables AI agents to directly manage Beyond Identity resources such as identities, groups, applications, SSO configurations, and credentials via natural language tool calls.362 npmApache 2.0

@volter/tunnel-mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to manage account, usage, and abuse operations for the Volter tunnel relay.276 npm2Apache 2.0- FlicenseAqualityDmaintenanceProvides AI agents with programmatic access to Zscaler AI Guard, enabling autonomous management of detection policies, match rules, LLM applications, and LLM providers.291-